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>https://people.skolelinux.org/pere/blog/
</link>
10 <title>The
2024 LinuxCNC Norwegian developer gathering
</title>
11 <link>https://people.skolelinux.org/pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html
</guid>
13 <pubDate>Fri,
31 May
2024 07:
45:
00 +
0200</pubDate>
14 <description><p
><a href=
"https://linuxcnc.org/
">The LinuxCNC project
</a
> is still
15 going strong. And I believe this great software system for numerical control of
16 machines such as milling machines, lathes, plasma cutters, routers,
17 cutting machines, robots and hexapods, would do even better with more
18 in-person developer gatherings, so we plan to organise such gathering
19 this summer too.
</p
>
21 <p
>The Norwegian LinuxCNC developer gathering take place the weekend
22 Friday July
5th to
7th this year, and is open for everyone interested
23 in contributing to LinuxCNC and free software manufacturing. Up to
24 date information about the gathering can be found in
25 <a href=
"https://sourceforge.net/p/emc/mailman/emc-developers/thread/
123eaae0-f3b9-
4170-a251-b7d608f1e974%
40bofh.no/
">the
26 developer mailing list thread
</a
> where the gathering was announced.
27 Thanks to the good people at
29 <a href=
"https://www.debian.org/
">Debian
</a
> as well as leftover money
30 from last years gathering from
31 <a href=
"https://www.redpill-linpro.com/
">Redpill-Linpro
</a
> and
32 <a href=
"https://www.nuugfoundation.no/no/
">NUUG Foundation
</a
>, we
33 have enough sponsor funds to pay for food, and probably also shelter
34 for the people traveling from afar to join us. If you would like to
35 join the gathering, get in touch and add your details on
36 <a href=
"https://pad.efn.no/p/linuxcnc-
2024-norway
">the pad
</a
>.
</p
>
38 <p
>As usual, if you use Bitcoin and want to show your support of my
39 activities, please send Bitcoin donations to my address
40 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
45 <title>45 orphaned Debian packages moved to git,
391 to go
</title>
46 <link>https://people.skolelinux.org/pere/blog/
45_orphaned_Debian_packages_moved_to_git__391_to_go.html
</link>
47 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/
45_orphaned_Debian_packages_moved_to_git__391_to_go.html
</guid>
48 <pubDate>Thu,
25 Apr
2024 22:
00:
00 +
0200</pubDate>
49 <description><p
>Nine days ago, I started migrating orphaned Debian packages with no
50 version control system listed in debian/control of the source to git.
51 At the time there were
438 such packages. Now there are
391,
52 according to the UDD. In reality it is slightly less, as there is a
53 delay between uploads and UDD updates. In the nine days since, I have
54 thus been able to work my way through ten percent of the packages. I
55 am starting to run out of steam, and hope someone else will also help
56 brushing some dust of these packages. Here is a recipe how to do it.
58 I start by picking a random package by querying the UDD for a list of
59 10 random packages from the set of remaining packages:
61 <blockquote
><pre
>
62 PGPASSWORD=
"udd-mirror
" psql --port=
5432 --host=udd-mirror.debian.net \
63 --username=udd-mirror udd -c
"select source from sources \
64 where release =
'sid
' and (vcs_url ilike
'%anonscm.debian.org%
' \
65 OR vcs_browser ilike
'%anonscm.debian.org%
' or vcs_url IS NULL \
66 OR vcs_browser IS NULL) AND maintainer ilike
'%packages@qa.debian.org%
' \
67 order by random() limit
10;
"
68 </pre
></blockquote
>
70 <p
>Next, I visit http://salsa.debian.org/debian and search for the
71 package name, to ensure no git repository already exist. If it does,
72 I clone it and try to get it to an uploadable state, and add the Vcs-*
73 entries in d/control to make the repository more widely known. These
74 packages are a minority, so I will not cover that use case here.
</p
>
76 <p
>For packages without an existing git repository, I run the
77 following script
<tt
>debian-snap-to-salsa
</tt
> to prepare a git
78 repository with the existing packaging.
</p
>
80 <blockquote
><pre
>
83 # See also https://bugs.debian.org/
804722#
31
87 # Move to this Standards-Version.
92 if [ -z
"$PKG
" ]; then
93 echo
"usage: $
0 <pkgname
>"
97 if [ -e
"${PKG}-salsa
" ]; then
98 echo
"error: ${PKG}-salsa already exist, aborting.
"
102 if [ -z
"ALLOWFAILURE
" ] ; then
106 # Fetch every snapshotted source package. Manually loop until all
107 # transfers succeed, as
'gbp import-dscs --debsnap
' do not fail on
109 until debsnap --force -v $PKG || $ALLOWFAILURE ; do sleep
1; done
110 mkdir ${PKG}-salsa; cd ${PKG}-salsa
113 # Specify branches to override any debian/gbp.conf file present in the
115 gbp import-dscs --debian-branch=master --upstream-branch=upstream \
116 --pristine-tar ../source-$PKG/*.dsc
118 # Add Vcs pointing to Salsa Debian project (must be manually created
120 if ! grep -q ^Vcs- debian/control ; then
121 awk
"BEGIN { s=
1 } /^\$/ { if (s==
1) { print \
"Vcs-Browser: https://salsa.debian.org/debian/$PKG\
"; print \
"Vcs-Git: https://salsa.debian.org/debian/$PKG.git\
" }; s=
0 } { print }
" < debian/control
> debian/control.new
&& mv debian/control.new debian/control
122 git commit -m
"Updated vcs in d/control to Salsa.
" debian/control
125 # Tell gbp to enforce the use of pristine-tar.
126 inifile +inifile debian/gbp.conf +create +section DEFAULT +key pristine-tar +value True
127 git add debian/gbp.conf
128 git commit -m
"Added d/gbp.conf to enforce the use of pristine-tar.
" debian/gbp.conf
130 # Update to latest Standards-Version.
131 SV=
"$(grep ^Standards-Version: debian/control|awk
'{print $
2}
')
"
132 if [ $SV_LATEST != $SV ]; then
133 sed -i
"s/\(Standards-Version: \)\(.*\)/\
1$SV_LATEST/
" debian/control
134 git commit -m
"Updated Standards-Version from $SV to $SV_LATEST.
" debian/control
137 if grep -q pkg-config debian/control; then
138 sed -i s/pkg-config/pkgconf/ debian/control
139 git commit -m
"Replaced obsolete pkg-config build dependency with pkgconf.
" debian/control
142 if grep -q libncurses5-dev debian/control; then
143 sed -i s/libncurses5-dev/libncurses-dev/ debian/control
144 git commit -m
"Replaced obsolete libncurses5-dev build dependency with libncurses-dev.
" debian/control
146 </pre
></blockquote
>
148 Some times the debsnap script fail to download some of the versions.
149 In those cases I investigate, and if I decide the failing versions
150 will not be missed, I call it using ALLOWFAILURE=true to ignore the
151 problem and create the git repository anyway.
</p
>
153 <p
>With the git repository in place, I do a test build (gbp
154 buildpackage) to ensure the build is actually working. If it does not
155 I pick a different package, or if the build failure is trivial to fix,
156 I fix it before continuing. At this stage I revisit
157 http://salsa.debian.org/debian and create the project under this group
158 for the package. I then follow the instructions to publish the local
159 git repository. Here is from a recent example:
</p
>
161 <blockquote
><pre
>
162 git remote add origin git@salsa.debian.org:debian/perl-byacc.git
163 git push --set-upstream origin master upstream pristine-tar
165 </pre
></blockquote
>
167 <p
>With a working build, I have a look at the build rules if I want to
168 remove some more dust. I normally try to move to debhelper compat
169 level
13, which involves removing debian/compat and modifying
170 debian/control to build depend on debhelper-compat (=
13). I also test
171 with
'Rules-Requires-Root: no
' in debian/control and verify in
172 debian/rules that hardening is enabled, and include all of these if
173 the package still build. If it fail to build with level
13, I try
174 with
12,
11,
10 and so on until I find a level where it build, as I do
175 not want to spend a lot of time fixing build issues.
</p
>
177 <p
>Some times, when I feel inspired, I make sure debian/copyright is
178 converted to the machine readable format, often by starting with
179 'debhelper -cc
' and then cleaning up the autogenerated content until
180 it matches realities. If I feel like it, I might also clean up
181 non-dh-based debian/rules files to use the short style dh build
184 <p
>Once I have removed all the dust I care to process for the package,
185 I run
'gbp dch
' to generate a debian/changelog entry based on the
186 commits done so far, run
'dch -r
' to switch from
'UNRELEASED
' to
187 'unstable
' and get an editor to make sure the
'QA upload
' marker is in
188 place and that all long commit descriptions are wrapped into sensible
189 lengths, run
'debcommit --release -a
' to commit and tag the new
190 debian/changelog entry, run
'debuild -S
' to build a source only
191 package, and
'dput ../perl-byacc_2.0-
10_source.changes
' to do the
192 upload. During the entire process, and many times per step, I run
193 'debuild
' to verify the changes done still work. I also some times
194 verify the set of built files using
'find debian
' to see if I can spot
195 any problems (like no file in usr/bin any more or empty package). I
196 also try to fix all lintian issues reported at the end of each
197 'debuild
' run.
</p
>
199 <p
>If I find Debian specific patches, I try to ensure their metadata
200 is fairly up to date and some times I even try to reach out to
201 upstream, to make the upstream project aware of the patches. Most of
202 my emails bounce, so the success rate is low. For projects with no
203 Homepage entry in debian/control I try to track down one, and for
204 packages with no debian/watch file I try to create one. But at least
205 for some of the packages I have been unable to find a functioning
206 upstream, and must skip both of these.
</p
>
208 <p
>If I could handle ten percent in nine days, twenty people could
209 complete the rest in less then five days. I use approximately twenty
210 minutes per package, when I have twenty minutes spare time to spend.
211 Perhaps you got twenty minutes to spare too?
</p
>
213 <p
>As usual, if you use Bitcoin and want to show your support of my
214 activities, please send Bitcoin donations to my address
215 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
217 <p
><strong
>Update
2024-
05-
04:
</strong
> There is
218 <a href=
"https://people.skolelinux.org/pere/blog/images/
2024-
05-
04-debian-snap-to-salsa.sh
">an
219 updated edition of my migration script
</a
>, last updated
220 2024-
05-
04.
</p
>
225 <title>Time to move orphaned Debian packages to git
</title>
226 <link>https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html
</link>
227 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html
</guid>
228 <pubDate>Sun,
14 Apr
2024 09:
30:
00 +
0200</pubDate>
229 <description><p
>There are several packages in Debian without a associated git
230 repository with the packaging history. This is unfortunate and it
231 would be nice if more of these would do so. Quote a lot of these are
232 without a maintainer, ie listed as maintained by the
233 '<a href=
"https://qa.debian.org/developer.php?email=packages%
40qa.debian.org
">Debian
234 QA Group
</a
>' place holder. In fact,
438 packages have this property
235 according to UDD (
<tt
>SELECT source FROM sources WHERE release =
'sid
'
236 AND (vcs_url ilike
'%anonscm.debian.org%
' OR vcs_browser ilike
237 '%anonscm.debian.org%
' or vcs_url IS NULL OR vcs_browser IS NULL) AND
238 maintainer ilike
'%packages@qa.debian.org%
';
</tt
>). Such packages can
239 be updated without much coordination by any Debian developer, as they
240 are considered orphaned.
</p
>
242 <p
>To try to improve the situation and reduce the number of packages
243 without associated git repository, I started a few days ago to search
244 out candiates and provide them with a git repository under the
245 'debian
' collaborative Salsa project. I started with the packages
246 pointing to obsolete Alioth git repositories, and am now working my
247 way across the ones completely without git references. In addition to
248 updating the Vcs-* debian/control fields, I try to update
249 Standards-Version, debhelper compat level, simplify d/rules, switch to
250 Rules-Requires-Root: no and fix lintian issues reported. I only
251 implement those that are trivial to fix, to avoid spending too much
252 time on each orphaned package. So far my experience is that it take
253 aproximately
20 minutes to convert a package without any git
254 references, and a lot more for packages with existing git repositories
255 incompatible with git-buildpackages.
</p
>
257 <p
>So far I have converted
10 packages, and I will keep going until I
258 run out of steam. As should be clear from the numbers, there is
259 enough packages remaining for more people to do the same without
260 stepping on each others toes. I find it useful to start by searching
261 for a git repo already on salsa, as I find that some times a git repo
262 has already been created, but no new version is uploaded to Debian
263 yet. In those cases I start with the existing git repository. I
264 convert to the git-buildpackage+pristine-tar workflow, and ensure a
265 debian/gbp.conf file with
"pristine-tar=True
" is added early, to avoid
266 uploading a orig.tar.gz with the wrong checksum by mistake. Did that
267 three times in the begin before I remembered my mistake.
</p
>
269 <p
>So, if you are a Debian Developer and got some spare time, perhaps
270 considering migrating some orphaned packages to git?
</p
>
272 <p
>As usual, if you use Bitcoin and want to show your support of my
273 activities, please send Bitcoin donations to my address
274 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
279 <title>New and improved sqlcipher in Debian for accessing Signal database
</title>
280 <link>https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html
</link>
281 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html
</guid>
282 <pubDate>Sun,
12 Nov
2023 12:
00:
00 +
0100</pubDate>
283 <description><p
>For a while now I wanted to have direct access to the
284 <a href=
"https://signal.org/
">Signal
</a
> database of messages and
285 channels of my Desktop edition of Signal. I prefer the enforced end
286 to end encryption of Signal these days for my communication with
287 friends and family, to increase the level of safety and privacy as
288 well as raising the cost of the mass surveillance government and
289 non-government entities practice these days. In August I came across
291 <a href=
"https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/
">recipe
292 on how to use sqlcipher to extract statistics from the Signal
293 database
</a
> explaining how to do this. Unfortunately this did not
294 work with the version of sqlcipher in Debian. The
295 <a href=
"http://tracker.debian.org/sqlcipher/
">sqlcipher
</a
>
296 package is a
"fork
" of the sqlite package with added support for
297 encrypted databases. Sadly the current Debian maintainer
298 <a href=
"https://bugs.debian.org/
961598">announced more than three
299 years ago that he did not have time to maintain sqlcipher
</a
>, so it
300 seemed unlikely to be upgraded by the maintainer. I was reluctant to
301 take on the job myself, as I have very limited experience maintaining
302 shared libraries in Debian. After waiting and hoping for a few
303 months, I gave up the last week, and set out to update the package. In
304 the process I orphaned it to make it more obvious for the next person
305 looking at it that the package need proper maintenance.
</p
>
307 <p
>The version in Debian was around five years old, and quite a lot of
308 changes had taken place upstream into the Debian maintenance git
309 repository. After spending a few days importing the new upstream
310 versions, realising that upstream did not care much for SONAME
311 versioning as I saw library symbols being both added and removed with
312 minor version number changes to the project, I concluded that I had to
313 do a SONAME bump of the library package to avoid surprising the
314 reverse dependencies. I even added a simple
315 autopkgtest script to ensure the package work as intended. Dug deep
316 into the hole of learning shared library maintenance, I set out a few
317 days ago to upload the new version to Debian experimental to see what
318 the quality assurance framework in Debian had to say about the result.
319 The feedback told me the pacakge was not too shabby, and yesterday I
320 uploaded the latest version to Debian unstable. It should enter
321 testing today or tomorrow, perhaps delayed by
322 <a href=
"https://bugs.debian.org/
1055812">a small library
323 transition
</a
>.
</p
>
325 <p
>Armed with a new version of sqlcipher, I can now have a look at the
326 SQL database in ~/.config/Signal/sql/db.sqlite. First, one need to
327 fetch the encryption key from the Signal configuration using this
328 simple JSON extraction command:
</p
>
330 <pre
>/usr/bin/jq -r
'.
"key
"' ~/.config/Signal/config.json
</pre
>
332 <p
>Assuming the result from that command is
'secretkey
', which is a
333 hexadecimal number representing the key used to encrypt the database.
334 Next, one can now connect to the database and inject the encryption
335 key for access via SQL to fetch information from the database. Here
336 is an example dumping the database structure:
</p
>
339 % sqlcipher ~/.config/Signal/sql/db.sqlite
340 sqlite
> PRAGMA key =
"x
'secretkey
'";
342 CREATE TABLE sqlite_stat1(tbl,idx,stat);
343 CREATE TABLE conversations(
344 id STRING PRIMARY KEY ASC,
352 , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
353 CREATE TABLE identityKeys(
354 id STRING PRIMARY KEY ASC,
358 id STRING PRIMARY KEY ASC,
361 CREATE TABLE sessions(
365 , ourServiceId STRING, serviceId STRING);
366 CREATE TABLE attachment_downloads(
367 id STRING primary key,
372 CREATE TABLE sticker_packs(
377 coverStickerId INTEGER,
379 downloadAttempts INTEGER,
383 stickerCount INTEGER,
385 , attemptedStatus STRING, position INTEGER DEFAULT
0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
386 INTEGER DEFAULT
0 NOT NULL);
387 CREATE TABLE stickers(
389 packId TEXT NOT NULL,
398 PRIMARY KEY (id, packId),
399 CONSTRAINT stickers_fk
401 REFERENCES sticker_packs(id)
404 CREATE TABLE sticker_references(
407 CONSTRAINT sticker_references_fk
409 REFERENCES sticker_packs(id)
413 shortName TEXT PRIMARY KEY,
416 CREATE TABLE messages(
417 rowid INTEGER PRIMARY KEY ASC,
423 schemaVersion INTEGER,
424 conversationId STRING,
427 hasAttachments INTEGER,
428 hasFileAttachments INTEGER,
429 hasVisualMediaAttachments INTEGER,
431 expirationStartTimestamp INTEGER,
434 messageTimer INTEGER,
435 messageTimerStart INTEGER,
436 messageTimerExpiresAt INTEGER,
439 sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
440 GENERATED ALWAYS AS (type IS
'story
'), isChangeCreatedByUs INTEGER NOT NULL DEFAULT
0, isTimerChangeFromSync INTEGER
441 GENERATED ALWAYS AS (
442 json_extract(json,
'$.expirationTimerUpdate.fromSync
') IS
1
443 ), seenStatus NUMBER default
0, storyDistributionListId STRING, expiresAt INT
446 expirationStartTimestamp + (expireTimer *
1000),
448 )), shouldAffectActivity INTEGER
449 GENERATED ALWAYS AS (
453 'change-number-notification
',
454 'contact-removed-notification
',
455 'conversation-merge
',
456 'group-v1-migration
',
458 'message-history-unsynced
',
459 'profile-change
',
461 'universal-timer-notification
',
462 'verified-change
'
464 ), shouldAffectPreview INTEGER
465 GENERATED ALWAYS AS (
469 'change-number-notification
',
470 'contact-removed-notification
',
471 'conversation-merge
',
472 'group-v1-migration
',
474 'message-history-unsynced
',
475 'profile-change
',
477 'universal-timer-notification
',
478 'verified-change
'
480 ), isUserInitiatedMessage INTEGER
481 GENERATED ALWAYS AS (
485 'change-number-notification
',
486 'contact-removed-notification
',
487 'conversation-merge
',
488 'group-v1-migration
',
489 'group-v2-change
',
491 'message-history-unsynced
',
492 'profile-change
',
494 'universal-timer-notification
',
495 'verified-change
'
497 ), mentionsMe INTEGER NOT NULL DEFAULT
0, isGroupLeaveEvent INTEGER
498 GENERATED ALWAYS AS (
499 type IS
'group-v2-change
' AND
500 json_array_length(json_extract(json,
'$.groupV2Change.details
')) IS
1 AND
501 json_extract(json,
'$.groupV2Change.details[
0].type
') IS
'member-remove
' AND
502 json_extract(json,
'$.groupV2Change.from
') IS NOT NULL AND
503 json_extract(json,
'$.groupV2Change.from
') IS json_extract(json,
'$.groupV2Change.details[
0].aci
')
504 ), isGroupLeaveEventFromOther INTEGER
505 GENERATED ALWAYS AS (
506 isGroupLeaveEvent IS
1
508 isChangeCreatedByUs IS
0
510 GENERATED ALWAYS AS (
511 json_extract(json,
'$.callId
')
513 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
516 queueType TEXT STRING NOT NULL,
517 timestamp INTEGER NOT NULL,
520 CREATE TABLE reactions(
521 conversationId STRING,
524 messageReceivedAt INTEGER,
525 targetAuthorAci STRING,
526 targetTimestamp INTEGER,
529 CREATE TABLE senderKeys(
530 id TEXT PRIMARY KEY NOT NULL,
531 senderId TEXT NOT NULL,
532 distributionId TEXT NOT NULL,
534 lastUpdatedDate NUMBER NOT NULL
536 CREATE TABLE unprocessed(
537 id STRING PRIMARY KEY ASC,
544 serverTimestamp INTEGER,
545 sourceServiceId STRING
546 , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
547 CREATE TABLE sendLogPayloads(
548 id INTEGER PRIMARY KEY ASC,
550 timestamp INTEGER NOT NULL,
551 contentHint INTEGER NOT NULL,
553 , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT
0 NOT NULL);
554 CREATE TABLE sendLogRecipients(
555 payloadId INTEGER NOT NULL,
557 recipientServiceId STRING NOT NULL,
558 deviceId INTEGER NOT NULL,
560 PRIMARY KEY (payloadId, recipientServiceId, deviceId),
562 CONSTRAINT sendLogRecipientsForeignKey
563 FOREIGN KEY (payloadId)
564 REFERENCES sendLogPayloads(id)
567 CREATE TABLE sendLogMessageIds(
568 payloadId INTEGER NOT NULL,
570 messageId STRING NOT NULL,
572 PRIMARY KEY (payloadId, messageId),
574 CONSTRAINT sendLogMessageIdsForeignKey
575 FOREIGN KEY (payloadId)
576 REFERENCES sendLogPayloads(id)
579 CREATE TABLE preKeys(
580 id STRING PRIMARY KEY ASC,
582 , ourServiceId NUMBER
583 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
584 CREATE TABLE signedPreKeys(
585 id STRING PRIMARY KEY ASC,
587 , ourServiceId NUMBER
588 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
591 category TEXT NOT NULL,
593 descriptionTemplate TEXT NOT NULL
595 CREATE TABLE badgeImageFiles(
596 badgeId TEXT REFERENCES badges(id)
599 'order
' INTEGER NOT NULL,
604 CREATE TABLE storyReads (
605 authorId STRING NOT NULL,
606 conversationId STRING NOT NULL,
607 storyId STRING NOT NULL,
608 storyReadDate NUMBER NOT NULL,
610 PRIMARY KEY (authorId, storyId)
612 CREATE TABLE storyDistributions(
613 id STRING PRIMARY KEY NOT NULL,
616 senderKeyInfoJson STRING
617 , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
618 CREATE TABLE storyDistributionMembers(
619 listId STRING NOT NULL REFERENCES storyDistributions(id)
622 serviceId STRING NOT NULL,
624 PRIMARY KEY (listId, serviceId)
626 CREATE TABLE uninstalled_sticker_packs (
627 id STRING NOT NULL PRIMARY KEY,
628 uninstalledAt NUMBER NOT NULL,
630 storageVersion NUMBER,
631 storageUnknownFields BLOB,
632 storageNeedsSync INTEGER NOT NULL
634 CREATE TABLE groupCallRingCancellations(
635 ringId INTEGER PRIMARY KEY,
636 createdAt INTEGER NOT NULL
638 CREATE TABLE IF NOT EXISTS
'messages_fts_data
'(id INTEGER PRIMARY KEY, block BLOB);
639 CREATE TABLE IF NOT EXISTS
'messages_fts_idx
'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
640 CREATE TABLE IF NOT EXISTS
'messages_fts_content
'(id INTEGER PRIMARY KEY, c0);
641 CREATE TABLE IF NOT EXISTS
'messages_fts_docsize
'(id INTEGER PRIMARY KEY, sz BLOB);
642 CREATE TABLE IF NOT EXISTS
'messages_fts_config
'(k PRIMARY KEY, v) WITHOUT ROWID;
643 CREATE TABLE edited_messages(
644 messageId STRING REFERENCES messages(id)
648 , conversationId STRING);
649 CREATE TABLE mentions (
650 messageId REFERENCES messages(id) ON DELETE CASCADE,
655 CREATE TABLE kyberPreKeys(
656 id STRING PRIMARY KEY NOT NULL,
657 json TEXT NOT NULL, ourServiceId NUMBER
658 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
659 CREATE TABLE callsHistory (
660 callId TEXT PRIMARY KEY,
661 peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
662 ringerId TEXT DEFAULT NULL, -- ringer uuid
663 mode TEXT NOT NULL, -- enum
"Direct
" |
"Group
"
664 type TEXT NOT NULL, -- enum
"Audio
" |
"Video
" |
"Group
"
665 direction TEXT NOT NULL, -- enum
"Incoming
" |
"Outgoing
666 -- Direct: enum
"Pending
" |
"Missed
" |
"Accepted
" |
"Deleted
"
667 -- Group: enum
"GenericGroupCall
" |
"OutgoingRing
" |
"Ringing
" |
"Joined
" |
"Missed
" |
"Declined
" |
"Accepted
" |
"Deleted
"
668 status TEXT NOT NULL,
669 timestamp INTEGER NOT NULL,
670 UNIQUE (callId, peerId) ON CONFLICT FAIL
672 [ dropped all indexes to save space in this blog post ]
673 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
675 new.body IS NOT NULL AND new.isViewOnce =
1
677 DELETE FROM messages_fts WHERE rowid = old.rowid;
679 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
680 WHEN new.isViewOnce IS NOT
1 AND new.storyId IS NULL
682 INSERT INTO messages_fts
685 (new.rowid, new.body);
687 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
688 DELETE FROM messages_fts WHERE rowid = old.rowid;
689 DELETE FROM sendLogPayloads WHERE id IN (
690 SELECT payloadId FROM sendLogMessageIds
691 WHERE messageId = old.id
693 DELETE FROM reactions WHERE rowid IN (
694 SELECT rowid FROM reactions
695 WHERE messageId = old.id
697 DELETE FROM storyReads WHERE storyId = old.storyId;
699 CREATE VIRTUAL TABLE messages_fts USING fts5(
701 tokenize =
'signal_tokenizer
'
703 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
705 (new.body IS NULL OR old.body IS NOT new.body) AND
706 new.isViewOnce IS NOT
1 AND new.storyId IS NULL
708 DELETE FROM messages_fts WHERE rowid = old.rowid;
709 INSERT INTO messages_fts
712 (new.rowid, new.body);
714 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
716 INSERT INTO mentions (messageId, mentionAci, start, length)
718 SELECT messages.id, bodyRanges.value -
>> 'mentionAci
' as mentionAci,
719 bodyRanges.value -
>> 'start
' as start,
720 bodyRanges.value -
>> 'length
' as length
721 FROM messages, json_each(messages.json -
>> 'bodyRanges
') as bodyRanges
722 WHERE bodyRanges.value -
>> 'mentionAci
' IS NOT NULL
724 AND messages.id = new.id;
726 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
728 DELETE FROM mentions WHERE messageId = new.id;
729 INSERT INTO mentions (messageId, mentionAci, start, length)
731 SELECT messages.id, bodyRanges.value -
>> 'mentionAci
' as mentionAci,
732 bodyRanges.value -
>> 'start
' as start,
733 bodyRanges.value -
>> 'length
' as length
734 FROM messages, json_each(messages.json -
>> 'bodyRanges
') as bodyRanges
735 WHERE bodyRanges.value -
>> 'mentionAci
' IS NOT NULL
737 AND messages.id = new.id;
742 <p
>Finally I have the tool needed to inspect and process Signal
743 messages that I need, without using the vendor provided client. Now
744 on to transforming it to a more useful format.
</p
>
746 <p
>As usual, if you use Bitcoin and want to show your support of my
747 activities, please send Bitcoin donations to my address
748 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
753 <title>New chrpath release
0.17</title>
754 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html
</link>
755 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html
</guid>
756 <pubDate>Fri,
10 Nov
2023 07:
30:
00 +
0100</pubDate>
757 <description><p
>The chrpath package provide a simple command line tool to remove or
758 modify the rpath or runpath of compiled ELF program. It is almost
10
759 years since I updated the code base, but I stumbled over the tool
760 today, and decided it was time to move the code base from Subversion
761 to git and find a new home for it, as the previous one (Debian Alioth)
762 has been shut down. I decided to go with
763 <a href=
"https://codeberg.org/
">Codeberg
</a
> this time, as it is my git
764 service of choice these days, did a quick and dirty migration to git
765 and updated the code with a few patches I found in the Debian bug
766 tracker. These are the release notes:
</p
>
768 <p
>New in
0.17 released
2023-
11-
10:
</p
>
771 <li
>Moved project to Codeberg, as Alioth is shut down.
</li
>
772 <li
>Add Solaris support (use
&lt;sys/byteorder.h
> instead of
&lt;byteswap.h
>).
773 Patch from Rainer Orth.
</li
>
774 <li
>Added missing newline from printf() line. Patch from Frank Dana.
</li
>
775 <li
>Corrected handling of multiple ELF sections. Patch from Frank Dana.
</li
>
776 <li
>Updated build rules for .deb. Partly based on patch from djcj.
</li
>
779 <p
>The latest edition is tagged and available from
780 <a href=
"https://codeberg.org/pere/chrpath
">https://codeberg.org/pere/chrpath
</a
>.
782 <p
>As usual, if you use Bitcoin and want to show your support of my
783 activities, please send Bitcoin donations to my address
784 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
789 <title>Test framework for DocBook processors / formatters
</title>
790 <link>https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</link>
791 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</guid>
792 <pubDate>Sun,
5 Nov
2023 13:
00:
00 +
0100</pubDate>
793 <description><p
>All the books I have published so far has been using
794 <a href=
"https://docbook.org/
">DocBook
</a
> somewhere in the process.
795 For the first book, the source format was DocBook, while for every
796 later book it was an intermediate format used as the stepping stone to
797 be able to present the same manuscript in several formats, on paper,
798 as ebook in ePub format, as a HTML page and as a PDF file either for
799 paper production or for Internet consumption. This is made possible
800 with a wide variety of free software tools with DocBook support in
801 Debian. The source format of later books have been docx via rst,
802 Markdown, Filemaker and Asciidoc, and for all of these I was able to
803 generate a suitable DocBook file for further processing using
804 <a href=
"https://tracker.debian.org/pkg/pandoc
">pandoc
</a
>,
805 <a href=
"https://tracker.debian.org/pkg/asciidoc
">a2x
</a
> and
806 <a href=
"https://tracker.debian.org/pkg/asciidoctor
">asciidoctor
</a
>,
807 as well as rendering using
808 <a href=
"https://tracker.debian.org/pkg/xmlto
">xmlto
</a
>,
809 <a href=
"https://tracker.debian.org/pkg/dbtoepub
">dbtoepub
</a
>,
810 <a href=
"https://tracker.debian.org/pkg/dblatex
">dblatex
</a
>,
811 <a href=
"https://tracker.debian.org/pkg/docbook-xsl
">docbook-xsl
</a
> and
812 <a href=
"https://tracker.debian.org/pkg/fop
">fop
</a
>.
</p
>
814 <p
>Most of the
<a href=
"http://www.hungry.com/~pere/publisher/
">books I
815 have published
</a
> are translated books, with English as the source
817 <a href=
"https://tracker.debian.org/pkg/po4a
">po4a
</a
> to
818 handle translations using the gettext PO format has been a blessing,
819 but publishing translated books had triggered the need to ensure the
820 DocBook tools handle relevant languages correctly. For every new
821 language I have published, I had to submit patches dblatex, dbtoepub
822 and docbook-xsl fixing incorrect language and country specific issues
823 in the framework themselves. Typically this has been missing keywords
824 like
'figure
' or sort ordering of index entries. After a while it
825 became tiresome to only discover issues like this by accident, and I
826 decided to write a DocBook
"test framework
" exercising various
827 features of DocBook and allowing me to see all features exercised for
828 a given language. It consist of a set of DocBook files, a version
4
829 book, a version
5 book, a v4 book set, a v4 selection of problematic
830 tables, one v4 testing sidefloat and finally one v4 testing a book of
831 articles. The DocBook files are accompanied with a set of build rules
832 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
833 or docbook-xsl and epub using dbtoepub. The result is a set of files
834 visualizing footnotes, indexes, table of content list, figures,
835 formulas and other DocBook features, allowing for a quick review on
836 the completeness of the given locale settings. To build with a
837 different language setting, all one need to do is edit the lang= value
838 in the .xml file to pick a different ISO
639 code value and run
839 'make
'.
</p
>
841 <p
>The
<a href=
"https://codeberg.org/pere/docbook-example/
">test framework
842 source code
</a
> is available from Codeberg, and a generated set of
843 presentations of the various examples is available as Codeberg static
845 <a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
>.
846 Using this test framework I have been able to discover and report
847 several bugs and missing features in various tools, and got a lot of
848 them fixed. For example I got Northern Sami keywords added to both
849 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
850 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
851 Norwegian index sorting support fixed in xindy and initial Norwegian
852 Bokmål support added to dblatex. Some issues still remains, though.
853 Default index sorting rules are still broken in several tools, so the
854 Norwegian letters æ, ø and å are more often than not sorted properly
855 in the book index.
</p
>
857 <p
>The test framework recently received some more polish, as part of
858 publishing my latest book. This book contained a lot of fairly
859 complex tables, which exposed bugs in some of the tools. This made me
860 add a new test file with various tables, as well as spend some time to
861 brush up the build rules. My goal is for the test framework to
862 exercise all DocBook features to make it easier to see which features
863 work with different processors, and hopefully get them all to support
864 the full set of DocBook features. Feel free to send patches to extend
865 the test set, and test it with your favorite DocBook processor.
866 Please visit these two URLs to learn more:
</p
>
869 <li
><a href=
"https://codeberg.org/pere/docbook-example/
">https://codeberg.org/pere/docbook-example/
</a
></li
>
870 <li
><a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
></li
>
873 <p
>If you want to learn more on Docbook and translations, I recommend
874 having a look at the
<a href=
"https://docbook.org/
">the DocBook
876 <a href=
"https://doccookbook.sourceforge.net/html/en/
">the DoCookBook
877 site
<a/
> and my earlier blog post on
878 <a href=
"https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
">how
879 the Skolelinux project process and translate documentation
</a
>, a talk I gave earlier this year on
880 <a href=
"https://www.nuug.no/aktiviteter/
20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/
">how
881 to translate and publish books using free software
</a
> (Norwegian
886 https://github.com/docbook/xslt10-stylesheets/issues/
205 (docbook-xsl: sme support)
887 https://bugs.debian.org/
968437 (xindy: index sorting rules for nb/nn)
888 https://bugs.debian.org/
856123 (pandoc: markdown to docbook with non-english titles)
889 https://bugs.debian.org/
864813 (dblatex: missing nb words)
890 https://bugs.debian.org/
756386 (dblatex: index sorting rules for nb/nn)
891 https://bugs.debian.org/
796871 (dbtoepub: index sorting rules for nb/nn)
892 https://bugs.debian.org/
792616 (dblatex: PDF metadata)
893 https://bugs.debian.org/
686908 (docbook-xsl: index sorting rules for nb/nn)
894 https://sourceforge.net/tracker/?func=detail
&atid=
373747&aid=
3556630&group_id=
21935 (docbook-xsl: nb/nn support)
895 https://bugs.debian.org/
684391 (dblatex: initial nb support)
899 <p
>As usual, if you use Bitcoin and want to show your support of my
900 activities, please send Bitcoin donations to my address
901 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
906 <title>What did I learn from OpenSnitch this summer?
</title>
907 <link>https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</link>
908 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</guid>
909 <pubDate>Sun,
11 Jun
2023 08:
30:
00 +
0200</pubDate>
910 <description><p
>With yesterdays
911 <a href=
"https://www.debian.org/News/
2023/
20230610">release of Debian
912 12 Bookworm
</a
>, I am happy to know the
913 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
914 application firewall OpenSnitch
</a
> is available for a wider audience.
915 I have been running it for a few weeks now, and have been surprised
916 about some of the programs connecting to the Internet. Some programs
917 are obviously calling out from my machine, like the NTP network based
918 clock adjusting system and Tor to reach other Tor clients, but others
919 were more dubious. For example, the KDE Window manager try to look up
920 the host name in DNS, for no apparent reason, but if this lookup is
921 blocked the KDE desktop get periodically stuck when I use it. Another
922 surprise was how much Firefox call home directly to mozilla.com,
923 mozilla.net and googleapis.com, to mention a few, when I visit other
924 web pages. This direct connection happen even if I told Firefox to
925 always use a proxy, and the proxy setting is ignored for this traffic.
926 Other surprising connections come from audacity and dirmngr (I do not
927 use Gnome). It took some trial and error to get a good default set of
928 permissions. Without it, I would get popups asking for permissions at
929 any time, also the most inconvenient ones where I am in the middle of
930 a time sensitive gaming session.
</p
>
932 <p
>I suspect some application developers should rethink when then need
933 to use network connections or DNS lookups, and recommend testing
934 OpenSnitch (only
<tt
>apt install opensnitch
</tt
> away in Debian
935 Bookworm) to locate and report any surprising Internet connections on
936 your desktop machine.
</p
>
938 <p
>At the moment the upstream developer and Debian package maintainer
939 is working on making the system more reliable in Debian, by enabling
940 the eBPF kernel module to track processes and connections instead of
941 depending in content in /proc/. This should enter unstable fairly
944 <p
>As usual, if you use Bitcoin and want to show your support of my
945 activities, please send Bitcoin donations to my address
946 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
948 <p
><strong
>Update
2023-
06-
12</strong
>: I got a tip about
949 <a href=
"https://wiki.debian.org/PrivacyIssues
">a list of privacy
950 issues in Free Software
</a
> and the
951 <a href=
"irc://irc.debian.org/%
23debian-privacy
">#debian-privacy IRC
952 channel
</a
> discussing these topics.
</p
>
958 <title>wmbusmeters, parse data from your utility meter - nice free software
</title>
959 <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</link>
960 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</guid>
961 <pubDate>Fri,
19 May
2023 21:
50:
00 +
0200</pubDate>
962 <description><p
>There is a European standard for reading utility meters like water,
963 gas, electricity or heat distribution meters. The
964 <a href=
"https://en.wikipedia.org/wiki/Meter-Bus
">Meter-Bus standard
965 (EN
13757-
2, EN
13757-
3 and EN
13757–
4)
</a
> provide a cross vendor way
966 to talk to and collect meter data. I ran into this standard when I
967 wanted to monitor some heat distribution meters, and managed to find
968 free software that could do the job. The meters in question broadcast
969 encrypted messages with meter information via radio, and the hardest
970 part was to track down the encryption keys from the vendor. With this
971 in place I could set up a MQTT gateway to submit the meter data for
974 <p
>The free software systems in question,
975 <a href=
"https://tracker.debian.org/pkg/rtl-wmbus
">rtl-wmbus
</a
> to
976 read the messages from a software defined radio, and
977 <a href=
"https://tracker.debian.org/pkg/wmbusmeters
">wmbusmeters
</a
> to
978 decrypt and decode the content of the messages, is working very well
979 and allowe me to get frequent updates from my meters. I got in touch
980 with upstream last year to see if there was any interest in publishing
981 the packages via Debian. I was very happy to learn that Fredrik
982 Öhrström volunteered to maintain the packages, and I have since
983 assisted him in getting Debian package build rules in place as well as
984 sponsoring the packages into the Debian archive. Sadly we completed
985 it too late for them to become part of the next stable Debian release
986 (Bookworm). The wmbusmeters package just cleared the NEW queue. It
987 will need some work to fix a built problem, but I expect Fredrik will
988 find a solution soon.
</p
>
990 <p
>If you got a infrastructure meter supporting the Meter Bus
991 standard, I strongly recommend having a look at these nice
994 <p
>As usual, if you use Bitcoin and want to show your support of my
995 activities, please send Bitcoin donations to my address
996 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1001 <title>The
2023 LinuxCNC Norwegian developer gathering
</title>
1002 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</link>
1003 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</guid>
1004 <pubDate>Sun,
14 May
2023 20:
30:
00 +
0200</pubDate>
1005 <description><p
>The LinuxCNC project is making headway these days. A lot of
1006 patches and issues have seen activity on
1007 <a href=
"https://github.com/LinuxCNC/linuxcnc/
">the project github
1008 pages
</a
> recently. A few weeks ago there was a developer gathering
1009 over at the
<a href=
"https://tormach.com/
">Tormach
</a
> headquarter in
1010 Wisconsin, and now we are planning a new gathering in Norway. If you
1011 wonder what LinuxCNC is, lets quote Wikipedia:
</p
>
1014 "LinuxCNC is a software system for numerical control of
1015 machines such as milling machines, lathes, plasma cutters, routers,
1016 cutting machines, robots and hexapods. It can control up to
9 axes or
1017 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
1018 several GUIs suited to specific kinds of usage (touch screen,
1019 interactive development).
"
1022 <p
>The Norwegian developer gathering take place the weekend June
16th
1023 to
18th this year, and is open for everyone interested in contributing
1024 to LinuxCNC. Up to date information about the gathering can be found
1026 <a href=
"https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%
40hjemme.reinholdtsen.name/#msg37837251
">the
1027 developer mailing list thread
</a
> where the gathering was announced.
1028 Thanks to the good people at
1029 <a href=
"https://www.debian.org/
">Debian
</a
>,
1030 <a href=
"https://www.redpill-linpro.com/
">Redpill-Linpro
</a
> and
1031 <a href=
"https://www.nuugfoundation.no/no/
">NUUG Foundation
</a
>, we
1032 have enough sponsor funds to pay for food, and shelter for the people
1033 traveling from afar to join us. If you would like to join the
1034 gathering, get in touch.
</p
>
1036 <p
>As usual, if you use Bitcoin and want to show your support of my
1037 activities, please send Bitcoin donations to my address
1038 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1043 <title>OpenSnitch in Debian ready for prime time
</title>
1044 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</link>
1045 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</guid>
1046 <pubDate>Sat,
13 May
2023 12:
10:
00 +
0200</pubDate>
1047 <description><p
>A bit delayed,
1048 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
1049 application firewall OpenSnitch
</a
> package in Debian now got the
1050 latest fixes ready for Debian Bookworm. Because it depend on a
1051 package missing on some architectures, the autopkgtest check of the
1052 testing migration script did not understand that the tests were
1053 actually working, so the migration was delayed. A bug in the package
1054 dependencies is also fixed, so those installing the firewall package
1055 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
1056 installed by default. I am very grateful to Gustavo Iñiguez Goya for
1057 his work on getting the package ready for Debian Bookworm.
</p
>
1059 <p
>Armed with this package I have discovered some surprising
1060 connections from programs I believed were able to work completly
1061 offline, and it has already proven its worth, at least to me. If you
1062 too want to get more familiar with the kind of programs using
1063 Internett connections on your machine, I recommend testing
<tt
>apt
1064 install opensnitch
</tt
> in Bookworm and see what you think.
</p
>
1066 <p
>The package is still not able to build its eBPF module within
1067 Debian. Not sure how much work it would be to get it working, but
1068 suspect some kernel related packages need to be extended with more
1069 header files to get it working.
</p
>
1071 <p
>As usual, if you use Bitcoin and want to show your support of my
1072 activities, please send Bitcoin donations to my address
1073 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1078 <title>Speech to text, she APTly whispered, how hard can it be?
</title>
1079 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</link>
1080 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</guid>
1081 <pubDate>Sun,
23 Apr
2023 09:
40:
00 +
0200</pubDate>
1082 <description><p
>While visiting a convention during Easter, it occurred to me that
1083 it would be great if I could have a digital Dictaphone with
1084 transcribing capabilities, providing me with texts to cut-n-paste into
1085 stuff I need to write. The background is that long drives often bring
1086 up the urge to write on texts I am working on, which of course is out
1087 of the question while driving. With the release of
1088 <a href=
"https://github.com/openai/whisper/
">OpenAI Whisper
</a
>, this
1089 seem to be within reach with Free Software, so I decided to give it a
1090 go. OpenAI Whisper is a Linux based neural network system to read in
1091 audio files and provide text representation of the speech in that
1092 audio recording. It handle multiple languages and according to its
1093 creators even can translate into a different language than the spoken
1094 one. I have not tested the latter feature. It can either use the CPU
1095 or a GPU with CUDA support. As far as I can tell, CUDA in practice
1096 limit that feature to NVidia graphics cards. I have few of those, as
1097 they do not work great with free software drivers, and have not tested
1098 the GPU option. While looking into the matter, I did discover some
1099 work to provide CUDA support on non-NVidia GPUs, and some work with
1100 the library used by Whisper to port it to other GPUs, but have not
1101 spent much time looking into GPU support yet. I
've so far used an old
1102 X220 laptop as my test machine, and only transcribed using its
1105 <p
>As it from a privacy standpoint is unthinkable to use computers
1106 under control of someone else (aka a
"cloud
" service) to transcribe
1107 ones thoughts and personal notes, I want to run the transcribing
1108 system locally on my own computers. The only sensible approach to me
1109 is to make the effort I put into this available for any Linux user and
1110 to upload the needed packages into Debian. Looking at Debian Bookworm, I
1111 discovered that only three packages were missing,
1112 <a href=
"https://bugs.debian.org/
1034307">tiktoken
</a
>,
1113 <a href=
"https://bugs.debian.org/
1034144">triton
</a
>, and
1114 <a href=
"https://bugs.debian.org/
1034091">openai-whisper
</a
>. For a while
1116 <a href=
"https://bugs.debian.org/
1034286">ffmpeg-python
</a
> was
1118 <a href=
"https://github.com/kkroening/ffmpeg-python/issues/
760">upstream
1119 seem to have vanished
</a
> I found it safer
1120 <a href=
"https://github.com/openai/whisper/pull/
1242">to rewrite
1121 whisper
</a
> to stop depending on in than to introduce ffmpeg-python
1122 into Debian. I decided to place these packages under the umbrella of
1123 <a href=
"https://salsa.debian.org/deeplearning-team
">the Debian Deep
1124 Learning Team
</a
>, which seem like the best team to look after such
1125 packages. Discussing the topic within the group also made me aware
1126 that the triton package was already a future dependency of newer
1127 versions of the torch package being planned, and would be needed after
1128 Bookworm is released.
</p
>
1130 <p
>All required code packages have been now waiting in
1131 <a href=
"https://ftp-master.debian.org/new.html
">the Debian NEW
1132 queue
</a
> since Wednesday, heading for Debian Experimental until
1133 Bookworm is released. An unsolved issue is how to handle the neural
1134 network models used by Whisper. The default behaviour of Whisper is
1135 to require Internet connectivity and download the model requested to
1136 <tt
>~/.cache/whisper/
</tt
> on first invocation. This obviously would
1137 fail
<a href=
"https://people.debian.org/~bap/dfsg-faq.html
">the
1138 deserted island test of free software
</a
> as the Debian packages would
1139 be unusable for someone stranded with only the Debian archive and solar
1140 powered computer on a deserted island.
</p
>
1142 <p
>Because of this, I would love to include the models in the Debian
1143 mirror system. This is problematic, as the models are very large
1144 files, which would put a heavy strain on the Debian mirror
1145 infrastructure around the globe. The strain would be even higher if
1146 the models change often, which luckily as far as I can tell they do
1147 not. The small model, which according to its creator is most useful
1148 for English and in my experience is not doing a great job there
1149 either, is
462 MiB (deb is
414 MiB). The medium model, which to me
1150 seem to handle English speech fairly well is
1.5 GiB (deb is
1.3 GiB)
1151 and the large model is
2.9 GiB (deb is
2.6 GiB). I would assume
1152 everyone with enough resources would prefer to use the large model for
1153 highest quality. I believe the models themselves would have to go
1154 into the non-free part of the Debian archive, as they are not really
1155 including any useful source code for updating the models. The
1156 "source
", aka the model training set, according to the creators
1157 consist of
"680,
000 hours of multilingual and multitask supervised
1158 data collected from the web
", which to me reads material with both
1159 unknown copyright terms, unavailable to the general public. In other
1160 words, the source is not available according to the Debian Free
1161 Software Guidelines and the model should be considered non-free.
</p
>
1163 <p
>I asked the Debian FTP masters for advice regarding uploading a
1164 model package on their IRC channel, and based on the feedback there it
1165 is still unclear to me if such package would be accepted into the
1166 archive. In any case I wrote build rules for a
1167 <a href=
"https://salsa.debian.org/deeplearning-team/openai-whisper-model
">OpenAI
1168 Whisper model package
</a
> and
1169 <a href=
"https://github.com/openai/whisper/pull/
1257">modified the
1170 Whisper code base
</a
> to prefer shared files under
<tt
>/usr/
</tt
> and
1171 <tt
>/var/
</tt
> over user specific files in
<tt
>~/.cache/whisper/
</tt
>
1172 to be able to use these model packages, to prepare for such
1173 possibility. One solution might be to include only one of the models
1174 (small or medium, I guess) in the Debian archive, and ask people to
1175 download the others from the Internet. Not quite sure what to do
1176 here, and advice is most welcome (use the debian-ai mailing list).
</p
>
1178 <p
>To make it easier to test the new packages while I wait for them to
1179 clear the NEW queue, I created an APT source targeting bookworm. I
1180 selected Bookworm instead of Bullseye, even though I know the latter
1181 would reach more users, is that some of the required dependencies are
1182 missing from Bullseye and I during this phase of testing did not want
1183 to backport a lot of packages just to get up and running.
</p
>
1185 <p
>Here is a recipe to run as user root if you want to test OpenAI
1186 Whisper using Debian packages on your Debian Bookworm installation,
1187 first adding the APT repository GPG key to the list of trusted keys,
1188 then setting up the APT repository and finally installing the packages
1189 and one of the models:
</p
>
1191 <p
><pre
>
1192 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
1193 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
1194 mkdir -p /etc/apt/sources.list.d
1195 cat
> /etc/apt/sources.list.d/pere-whisper.list
&lt;
&lt;EOF
1196 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
1197 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
1200 apt install openai-whisper
1201 </pre
></p
>
1203 <p
>The package work for me, but have not yet been tested on any other
1204 computer than my own. With it, I have been able to (badly) transcribe
1205 a
2 minute
40 second Norwegian audio clip to test using the small
1206 model. This took
11 minutes and around
2.2 GiB of RAM. Transcribing
1207 the same file with the medium model gave a accurate text in
77 minutes
1208 using around
5.2 GiB of RAM. My test machine had too little memory to
1209 test the large model, which I believe require
11 GiB of RAM. In
1210 short, this now work for me using Debian packages, and I hope it will
1211 for you and everyone else once the packages enter Debian.
</p
>
1213 <p
>Now I can start on the audio recording part of this project.
</p
>
1215 <p
>As usual, if you use Bitcoin and want to show your support of my
1216 activities, please send Bitcoin donations to my address
1217 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1222 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software
</title>
1223 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</link>
1224 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</guid>
1225 <pubDate>Fri,
7 Apr
2023 23:
10:
00 +
0200</pubDate>
1226 <description><p
>Today I finally found time to track down a useful radio frequency
1227 scanner for my software defined radio. Just for fun I tried to locate
1228 the radios used in the areas, and a good start would be to scan all
1229 the frequencies to see what is in use. I
've tried to find a useful
1230 program earlier, but ran out of time before I managed to find a useful
1231 tool. This time I was more successful, and after a few false leads I
1232 found a description of
1233 <a href=
"https://www.kali.org/tools/rtlsdr-scanner/
">rtlsdr-scanner
1234 over at the Kali site
</a
>, and was able to track down
1235 <a href=
"https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git
">the
1236 Kali package git repository
</a
> to build a deb package for the
1237 scanner. Sadly the package is missing from the Debian project itself,
1238 at least in Debian Bullseye. Two runtime dependencies,
1239 <a href=
"https://gitlab.com/kalilinux/packages/python-visvis.git
">python-visvis
</a
>
1241 <a href=
"https://gitlab.com/kalilinux/packages/python-rtlsdr.git
">python-rtlsdr
</a
>
1242 had to be built and installed separately. Luckily
'<tt
>gbp
1243 buildpackage
</tt
>' handled them just fine and no further packages had
1244 to be manually built. The end result worked out of the box after
1245 installation.
</p
>
1247 <p
>My initial scans for FM channels worked just fine, so I knew the
1248 scanner was functioning. But when I tried to scan every frequency
1249 from
100 to
1000 MHz, the program stopped unexpectedly near the
1250 completion. After some debugging I discovered USB software radio I
1251 used rejected frequencies above
948 MHz, triggering a unreported
1252 exception breaking the scan. Changing the scan to end at
957 worked
1253 better. I similarly found the lower limit to be around
15, and ended
1254 up with the following full scan:
</p
>
1256 <p
><a href=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
" width=
"100%
"></a
></p
>
1258 <p
>Saving the scan did not work, but exporting it as a CSV file worked
1259 just fine. I ended up with around
477k CVS lines with dB level for
1260 the given frequency.
</p
>
1262 <p
>The save failure seem to be a missing UTF-
8 encoding issue in the
1263 python code. Will see if I can find time to send a patch
1264 <a href=
"https://github.com/CdeMills/RTLSDR-Scanner/
">upstream
</a
>
1265 later to fix this exception:
</p
>
1268 Traceback (most recent call last):
1269 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
1270 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
1271 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
1272 handle.write(json.dumps(data, indent=
4))
1273 TypeError: a bytes-like object is required, not
'str
'
1274 Traceback (most recent call last):
1275 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
1276 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
1277 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
1278 handle.write(json.dumps(data, indent=
4))
1279 TypeError: a bytes-like object is required, not
'str
'
1282 <p
>As usual, if you use Bitcoin and want to show your support of my
1283 activities, please send Bitcoin donations to my address
1284 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1289 <title>OpenSnitch available in Debian Sid and Bookworm
</title>
1290 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</link>
1291 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</guid>
1292 <pubDate>Sat,
25 Feb
2023 20:
30:
00 +
0100</pubDate>
1293 <description><p
>Thanks to the efforts of the OpenSnitch lead developer Gustavo
1294 Iñiguez Goya allowing me to sponsor the upload,
1295 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
1296 application firewall OpenSnitch
</a
> is now available in Debian
1297 Testing, soon to become the next stable release of Debian.
</p
>
1299 <p
>This is a package which set up a network firewall on one or more
1300 machines, which is controlled by a graphical user interface that will
1301 ask the user if a program should be allowed to connect to the local
1302 network or the Internet. If some background daemon is trying to dial
1303 home, it can be blocked from doing so with a simple mouse click, or by
1304 default simply by not doing anything when the GUI question dialog pop
1305 up. A list of all programs discovered using the network is provided
1306 in the GUI, giving the user an overview of how the machine(s) programs
1307 use the network.
</p
>
1309 <p
>OpenSnitch was uploaded for NEW processing about a month ago, and I
1310 had little hope of it getting accepted and shaping up in time for the
1311 package freeze, but the Debian ftpmasters proved to be amazingly quick
1312 at checking out the package and it was accepted into the archive about
1313 week after the first upload. It is now team maintained under the Go
1314 language team umbrella. A few fixes to the default setup is only in
1315 Sid, and should migrate to Testing/Bookworm in a week.
</p
>
1317 <p
>During testing I ran into an
1318 <a href=
"https://github.com/evilsocket/opensnitch/issues/
813">issue
1319 with Minecraft server broadcasts disappearing
</a
>, which was quickly
1320 resolved by the developer with a patch and a proposed configuration
1321 change. I
've been told this was caused by the Debian packages default
1322 use if /proc/ information to track down kernel status, instead of the
1323 newer eBPF module that can be used. The reason is simply that
1324 upstream and I have failed to find a way to build the eBPF modules for
1325 OpenSnitch without a complete configured Linux kernel source tree,
1326 which as far as we can tell is unavailable as a build dependency in
1327 Debian. We tried unsuccessfully so far to use the kernel-headers
1328 package. It would be great if someone could provide some clues how to
1329 build eBPF modules on build daemons in Debian, possibly without the full
1330 kernel source.
</p
>
1332 <p
>As usual, if you use Bitcoin and want to show your support of my
1333 activities, please send Bitcoin donations to my address
1334 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1339 <title>Is the desktop recommending your program for opening its files?
</title>
1340 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
1341 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
1342 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
1343 <description><p
>Linux desktop systems
1344 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
1345 standardized
</a
> how programs present themselves to the desktop
1346 system. If a package include a .desktop file in
1347 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
1348 environments will pick up the file and use its content to generate the
1349 menu of available programs in the system. A lesser known fact is that
1350 a package can also explain to the desktop system how to recognize the
1351 files created by the program in question, and use it to open these
1352 files on request, for example via a GUI file browser.
</p
>
1354 <p
>A while back I ran into a package that did not tell the desktop
1355 system how to recognize its files and was not used to open its files
1356 in the file browser and fixed it. In the process I wrote a simple
1357 debian/tests/ script to ensure the setup keep working. It might be
1358 useful for other packages too, to ensure any future version of the
1359 package keep handling its own files.
</p
>
1361 <p
>For this to work the file format need a useful MIME type that can
1362 be used to identify the format. If the file format do not yet have a
1363 MIME type, it should define one and preferably also
1364 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
1365 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
1367 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
1368 query the database of standardized package information and ensure it
1369 return sensible values. It also need the location of an example file
1370 for xdg-mime to guess the format of.
</p
>
1375 # Author: Petter Reinholdtsen
1376 # License: GPL v2 or later at your choice.
1378 # Validate the MIME setup, making sure motor types have
1379 # application/vnd.openmotor+yaml associated with them and is connected
1380 # to the openmotor desktop file.
1384 mimetype=
"application/vnd.openmotor+yaml
"
1385 testfile=
"test/data/real/o3100/motor.ric
"
1386 mydesktopfile=
"openmotor.desktop
"
1388 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
1390 if [
"$mimetype
" !=
"$filemime
" ] ; then
1392 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
1394 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
1397 desktop=$(xdg-mime query default
"$mimetype
")
1399 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
1401 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
1403 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
1409 <p
>It is a simple way to ensure your users are not very surprised when
1410 they try to open one of your file formats in their file browser.
</p
>
1412 <p
>As usual, if you use Bitcoin and want to show your support of my
1413 activities, please send Bitcoin donations to my address
1414 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1419 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
1420 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
1421 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
1422 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
1423 <description><p
>While reading a
1424 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
1425 post claiming MacOS X recently started scanning local files and
1426 reporting information about them to Apple
</a
>, even on a machine where
1427 all such callback features had been disabled, I came across a
1428 description of the Little Snitch application for MacOS X. It seemed
1429 like a very nice tool to have in the tool box, and I decided to see if
1430 something similar was available for Linux.
</p
>
1432 <p
>It did not take long to find
1433 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
1434 package
</a
>, which has been in development since
2017, and now is in
1435 version
1.5.0. It has had a
1436 <a href=
"https://bugs.debian.org/
909567">request for Debian
1437 packaging
</a
> since
2018, but no-one completed the job so far. Just
1438 for fun, I decided to see if I could help, and I was very happy to
1440 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
1441 want a Debian package too
</a
>.
</p
>
1443 <p
>After struggling a bit with getting the program to run, figuring
1444 out building Go programs (and a little failed detour to look at eBPF
1445 builds too - help needed), I am very happy to report that I am
1446 sponsoring upstream to maintain the package in Debian, and it has
1447 since this morning been waiting in NEW for the ftpmasters to have a
1448 look. Perhaps it can get into the archive in time for the Bookworm
1451 <p
>As usual, if you use Bitcoin and want to show your support of my
1452 activities, please send Bitcoin donations to my address
1453 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1458 <title>LinuxCNC MQTT publisher component
</title>
1459 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
1460 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
1461 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
1462 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
1463 video from Andreas Schiffler
</a
> the other day, where he set up
1464 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
1465 information to the MQTT broker IBM Bluemix. As I also use MQTT for
1466 graphing, it occured to me that a generic MQTT LinuxCNC component
1467 would be useful and I set out to implement it. Today I got the first
1468 draft limping along and submitted as
1469 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
1470 LinuxCNC project
</a
>.
</p
>
1472 <p
>The simple part was setting up the MQTT publishing code in Python.
1473 I already have set up other parts submitting data to my Mosquito MQTT
1474 broker, so I could reuse that code. Writing a LinuxCNC component in
1475 Python as new to me, but using existing examples in the code
1476 repository and the extensive documentation, this was fairly straight
1477 forward. The hardest part was creating a automated test for the
1478 component to ensure it was working. Testing it in a simulated
1479 LinuxCNC machine proved very useful, as I discovered features I needed
1480 that I had not thought of yet, and adjusted the code quite a bit to
1481 make it easier to test without a operational MQTT broker
1482 available.
</p
>
1484 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
1485 pins I should collect and publish by default (in other words, the
1486 default set of information pieces published), and how to get the
1487 machine name from the LinuxCNC INI file. The latter is a minor
1488 detail, but I expect it would be useful in a setup with several
1489 machines available. I am hoping for feedback from the experienced
1490 LinuxCNC developers and users, to make the component even better
1491 before it can go into the mainland LinuxCNC code base.
</p
>
1493 <p
>Since I started on the MQTT component, I came across
1494 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
1495 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
1496 controlled by a Raspberry Pi, and it occured to me that it would
1497 be useful for such use cases if LinuxCNC also provided a REST API for
1498 querying its status. I hope to start on such component once the MQTT
1499 component is working well.
</p
>
1501 <p
>As usual, if you use Bitcoin and want to show your support of my
1502 activities, please send Bitcoin donations to my address
1503 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1508 <title>ONVIF IP camera management tool finally in Debian
</title>
1509 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
1510 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
1511 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
1512 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
1513 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
1514 specification
</a
>. There is finally a nice command line and GUI tool
1515 in Debian to manage ONVIF IP cameras. After working with upstream for
1516 a few months and sponsoring the upload, I am very happy to report that
1517 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
1518 entered Debian Sid last night.
</p
>
1520 <p
>The package provide a C library to communicate with such cameras, a
1521 command line tool to locate and update settings of (like password) the
1522 cameras and a GUI tool to configure and control the units as well as
1523 preview the video from the camera. Libonvif is available on Both
1524 Linux and Windows and the GUI tool uses the Qt library. The main
1525 competitors are non-free software, while libonvif is GNU GPL licensed.
1526 I am very glad Debian users in the future can control their cameras
1527 using a free software system provided by Debian. But the ONVIF world
1528 is full of slightly broken firmware, where the cameras pretend to
1529 follow the ONVIF specification but fail to set some configuration
1530 values or refuse to provide video to more than one recipient at the
1531 time, and the onvif project is quite young and might take a while
1532 before it completely work with your camera. Upstream seem eager to
1533 improve the library, so handling any broken camera might be just
<a
1534 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
1536 <p
>The package just cleared NEW, and need a new source only upload
1537 before it can enter testing. This will happen in the next few
1540 <p
>As usual, if you use Bitcoin and want to show your support of my
1541 activities, please send Bitcoin donations to my address
1542 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1547 <title>Managing and using ONVIF IP cameras with Linux
</title>
1548 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
1549 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
1550 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
1551 <description><p
>Recently I have been looking at how to control and collect data
1552 from a handful IP cameras using Linux. I both wanted to change their
1553 settings and to make their imagery available via a free software
1554 service under my control. Here is a summary of the tools I found.
</p
>
1556 <p
>First I had to identify the cameras and their protocols. As far as
1557 I could tell, they were using some SOAP looking protocol and their
1558 internal web server seem to only work with Microsoft Internet Explorer
1559 with some proprietary binary plugin, which in these days of course is
1560 a security disaster and also made it impossible for me to use the
1561 camera web interface. Luckily I discovered that the SOAP looking
1562 protocol is actually following
<a href=
"https://www.onvif.org/
">the
1563 ONVIF specification
</a
>, which seem to be supported by a lot of IP
1564 cameras these days.
</p
>
1566 <p
>Once the protocol was identified, I was able to find what appear to
1567 be the most popular way to configure ONVIF cameras, the free software
1569 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
1570 Manager
</a
>. Lacking any other options at the time, I tried
1571 unsuccessfully to get it running using Wine, but was missing a dotnet
1572 40 library and I found no way around it to run it on Linux.
</p
>
1574 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
1575 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
1576 Device Tool
</a
>. I did not like its terms of use, so did not spend
1577 much time on it.
</p
>
1579 <p
>To collect the video and make it available in a web interface, I
1580 found the Zoneminder tool in Debian. A recent version was able to
1581 automatically detect and configure ONVIF devices, so I could use it to
1582 set up motion detection in and collection of the camera output. I had
1583 initial problems getting the ONVIF autodetection to work, as both
1584 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
1585 the inter-tab communication
</a
> being used by the Zoneminder web
1586 pages, but managed to get konqueror to work. Apparently the
"Enhanced
1587 Tracking Protection
" in Firefox cause the problem. I ended up
1588 upgrading to the Bookworm edition of Zoneminder in the process to try
1589 to fix the issue, and believe the problem might be solved now.
</p
>
1591 <p
>In the process I came across the nice Linux GUI tool
1592 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
1593 allowing me to preview the camera output and validate the login
1594 passwords required. Sadly its author has grown tired of maintaining
1595 the software, so it might not see any future updates. Which is sad,
1596 as the viewer is sightly unstable and the picture tend to lock up.
1597 Note, this lockup might be due to limitations in the cameras and not
1598 the viewer implementation. I suspect the camera is only able to
1599 provide pictures to one client at the time, and the Zoneminder feed
1600 might interfere with the GUI viewer. I have
1601 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
1602 included in Debian
</a
>.
</p
>
1604 <p
>Finally, I found what appear to be very nice Linux free software
1605 replacement for the Windows tool, named
1606 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
1607 provide a C library to talk to ONVIF devices as well as a command line
1608 and GUI tool using the library. Using the GUI tool I was able to change
1609 the admin passwords and update other settings of the cameras. I have
1610 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
1611 included in Debian
</a
>.
</p
>
1613 <p
>As usual, if you use Bitcoin and want to show your support of my
1614 activities, please send Bitcoin donations to my address
1615 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1617 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
1618 this text, I got several suggestions for more free software Linux
1619 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
1620 ONVIF python library
</a
> (already
1621 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
1622 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
1623 fork
</a
> using a different SOAP dependency. There is also
1624 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
1625 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
1626 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
1627 two are not included in Debian either. I have not tested any of these
1633 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
1634 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
1635 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
1636 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
1637 <description><p align=
"center
"><img align=
"center
" src=
"https://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
1639 <p
>(The picture is of the previous edition.)
</p
>
1641 <p
>Almost two years after the previous Norwegian Bokmål translation of
1642 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1643 Handbook
</a
>" was published, a new edition is finally being prepared. The
1644 english text is updated, and it is time to start working on the
1645 translations. Around
37 percent of the strings have been updated, one
1646 way or another, and the translations starting from a complete Debian Buster
1647 edition now need to bring their translation up from
63% to
100%. The
1648 complete book is licensed using a Creative Commons license, and has
1649 been published in several languages over the years. The translations
1650 are done by volunteers to bring Linux in their native tongue. The
1651 last time I checked, it complete text was available in English,
1652 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
1653 In addition, work has been started for Arabic (Morocco), Catalan,
1654 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
1655 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
1656 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
1658 <p
>The translation is conducted on
1659 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1660 hosted weblate project page
</a
>. Prospective translators are
1661 recommeded to subscribe to
1662 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1663 translators mailing list
</a
> and should also check out
1664 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1665 contributors
</a
>.
</p
>
1667 <p
>I am one of the Norwegian Bokmål translators of this book, and we
1668 have just started. Your contribution is most welcome.
</p
>
1670 <p
>As usual, if you use Bitcoin and want to show your support of my
1671 activities, please send Bitcoin donations to my address
1672 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1677 <title>Automatic LinuxCNC servo PID tuning?
</title>
1678 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
1679 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
1680 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
1681 <description><p
>While working on a CNC with servo motors controlled by the
1682 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
1683 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
1684 controller
</a
>, I recently had to learn how to tune the collection of values
1685 that control such mathematical machinery that a PID controller is. It
1686 proved to be a lot harder than I hoped, and I still have not succeeded
1687 in getting the Z PID controller to successfully defy gravity, nor X
1688 and Y to move accurately and reliably. But while climbing up this
1689 rather steep learning curve, I discovered that some motor control
1690 systems are able to tune their PID controllers. I got the impression
1691 from the documentation that LinuxCNC were not. This proved to be not
1694 <p
>The LinuxCNC
1695 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
1696 component
</a
> is the recommended PID controller to use. It uses eight
1697 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
1698 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
1699 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
1700 state, and all of these need to have a sensible value for the
1701 controller to behave properly. Note, there are even more values
1702 involved, theser are just the most important ones. In my case I need
1703 the X, Y and Z axes to follow the requested path with little error.
1704 This has proved quite a challenge for someone who have never tuned a
1705 PID controller before, but there is at least some help to be found.
1707 <p
>I discovered that included in LinuxCNC was this old PID component
1708 at_pid claiming to have auto tuning capabilities. Sadly it had been
1709 neglected since
2011, and could not be used as a plug in replacement
1710 for the default pid component. One would have to rewriting the
1711 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
1712 to quickly test auto tuning to see if it did a better job than me at
1713 figuring out good P, I and D values to use.
</p
>
1715 <p
>I decided to have a look if the situation could be improved. This
1716 involved trying to understand the code and history of the pid and
1717 at_pid components. Apparently they had a common ancestor, as code
1718 structure, comments and variable names were quite close to each other.
1719 Sadly this was not reflected in the git history, making it hard to
1720 figure out what really happened. My guess is that the author of
1721 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
1723 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
1724 rewrote it to follow the structure he wished pid.c to have, then added
1725 support for auto tuning and finally got it included into the LinuxCNC
1726 repository. The restructuring and lack of early history made it
1727 harder to figure out which part of the code were relevant to the auto
1728 tuning, and which part of the code needed to be updated to work the
1729 same way as the current pid.c implementation. I started by trying to
1730 isolate relevant changes in pid.c, and applying them to at_pid.c. My
1731 aim was to make sure the at_pid component could replace the pid
1732 component with a simple change in the HAL setup loadrt line, without
1733 having to
"rewire
" the rest of the HAL configuration. After a few
1734 hours following this approach, I had learned quite a lot about the
1735 code structure of both components, while concluding I was heading down
1736 the wrong rabbit hole, and should get back to the surface and find a
1737 different path.
</p
>
1739 <p
>For the second attempt, I decided to throw away all the PID control
1740 related part of the original at_pid.c, and instead isolate and lift
1741 the auto tuning part of the code and inject it into a copy of pid.c.
1742 This ensured compatibility with the current pid component, while
1743 adding auto tuning as a run time option. To make it easier to identify
1744 the relevant parts in the future, I wrapped all the auto tuning code
1745 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
1746 pid component by default, as that part of the code is identical. The
1747 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
1748 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
1750 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
1751 component. The most important ones are
<tt
>tune-effort
</tt
>,
1752 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
1753 back, and see what the auto tuning code will do. I do not know the
1754 mathematical foundation of the at_pid algorithm, but from observation
1755 I can tell that the algorithm will, when enabled, produce a square
1756 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
1757 of the PID controller. This can be seen using the HAL Scope provided
1758 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
1759 to the motor controller, which in turn is translated into motor speed.
1760 So at_pid will ask the motor to move the axis back and forth. The
1761 number of cycles in the pattern is controlled by the
1762 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
1763 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
1764 change the direction of a physical object instantly (as in going
1765 directly from a positive voltage to the equivalent negative voltage)
1766 do not change velocity instantly, and it take some time for the object
1767 to slow down and move in the opposite direction. This result in a
1768 more smooth movement wave form, as the axis in question were vibrating
1769 back and forth. When the axis reached the target speed in the
1770 opposing direction, the auto tuner change direction again. After
1771 several of these changes, the average time delay between the
'peaks
'
1772 and
'valleys
' of this movement graph is then used to calculate
1773 proposed values for Pgain, Igain and Dgain, and insert them into the
1774 HAL model to use by the pid controller. The auto tuned settings are
1775 not great, but htye work a lot better than the values I had been able
1776 to cook up on my own, at least for the horizontal X and Y axis. But I
1777 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
1778 controllers error out if the voltage change too quickly. I
've been
1779 less lucky with the Z axis, which is moving a heavy object up and
1780 down, and seem to confuse the algorithm. The Z axis movement became a
1781 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
1782 gravitational drag, but I will have to work a lot more on the Z axis
1783 PID values.
</p
>
1785 <p
>Armed with this knowledge, it is time to look at how to do the
1786 tuning. Lets say the HAL configuration in question load the PID
1787 component for X, Y and Z like this:
</p
>
1789 <blockquote
><pre
>
1790 loadrt pid names=pid.x,pid.y,pid.z
1791 </pre
></blockquote
>
1793 <p
>Armed with the new and improved at_pid component, the new line will
1794 look like this:
</p
>
1796 <blockquote
><pre
>
1797 loadrt at_pid names=pid.x,pid.y,pid.z
1798 </pre
></blockquote
>
1800 <p
>The rest of the HAL setup can stay the same. This work because the
1801 components are referenced by name. If the component had used count=
3
1802 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
1804 <p
>To start tuning the X axis, move the axis to the middle of its
1805 range, to make sure it do not hit anything when it start moving back
1806 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
1807 output range. I used
0.1 as my initial value. Next, assign
1 to the
1808 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
1809 part and feed
0 to the output pin, which in my case initially caused a
1810 lot of drift. In my case it proved to be a good idea with X and Y to
1811 tune the motor driver to make sure
0 voltage stopped the motor
1812 rotation. On the other hand, for the Z axis this proved to be a bad
1813 idea, so it will depend on your setup. It might help to set the
1814 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
1815 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
1816 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
1817 your axis will vibrate for a few seconds and when it is done, new
1818 values for Pgain, Igain and Dgain will be active. To test them,
1819 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
1820 machine to suddenly jerk as it bring the axis back to its commanded
1821 position, which it might have drifted away from during tuning. To
1822 summarize with some halcmd lines:
</p
>
1824 <blockquote
><pre
>
1825 setp pid.x.tune-effort
0.1
1826 setp pid.x.tune-mode
1
1827 setp pid.x.tune-start
1
1828 # wait for the tuning to complete
1829 setp pid.x.tune-mode
0
1830 </pre
></blockquote
>
1832 <p
>After doing this task quite a few times while trying to figure out
1833 how to properly tune the PID controllers on the machine in, I decided
1834 to figure out if this process could be automated, and wrote a script
1835 to do the entire tuning process from power on. The end result will
1836 ensure the machine is powered on and ready to run, home all axis if it
1837 is not already done, check that the extra tuning pins are available,
1838 move the axis to its mid point, run the auto tuning and re-enable the
1839 pid controller when it is done. It can be run several times. Check
1841 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
1842 script on github if you want to learn how it is done.
</p
>
1844 <p
>My hope is that this little adventure can inspire someone who know
1845 more about motor PID controller tuning can implement even better
1846 algorithms for automatic PID tuning in LinuxCNC, making life easier
1847 for both me and all the others that want to use LinuxCNC but lack the
1848 in depth knowledge needed to tune PID controllers well.
</p
>
1850 <p
>As usual, if you use Bitcoin and want to show your support of my
1851 activities, please send Bitcoin donations to my address
1852 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1857 <title>LinuxCNC translators life just got a bit easier
</title>
1858 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
1859 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
1860 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
1861 <description><p
>Back in oktober last year, when I started looking at the
1862 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
1863 proposed to change the documentation build system make life easier for
1864 translators. The original system consisted of independently written
1865 documentation files for each language, with no automated way to track
1866 changes done in other translations and no help for the translators to
1867 know how much was left to translated. By using
1868 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
1869 files from the English documentation, this can be improved. A small
1870 team of LinuxCNC contributors got together and today our labour
1871 finally payed off. Since a few hours ago, it is now possible to
1872 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
1873 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
1875 <p
>The effort to migrate the documentation to use po4a has been both
1876 slow and frustrating. I am very happy we finally made it.
</p
>
1878 <p
>As usual, if you use Bitcoin and want to show your support of my
1879 activities, please send Bitcoin donations to my address
1880 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1885 <title>geteltorito make CD firmware upgrades a breeze
</title>
1886 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
1887 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
1888 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
1889 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
1890 located the firmware download page from Lenovo (which annoyingly do
1891 not allow access via Tor, forcing me to hand them more personal
1892 information that I would like). The
1893 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
1894 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
1895 when all I got available is a USB memory stick. I tried booting the
1896 ISO as a USB stick, but this did not work. But genisoimage came to
1897 the rescue.
</p
>
1899 <P
>The geteltorito program in
1900 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
1901 package
</a
> is able to convert the bootable ISO image to a bootable
1902 USB stick using a simple command line recipe, which I then can write
1903 to the most recently inserted USB stick:
</p
>
1905 <blockquote
><pre
>
1906 geteltorito -o usbstick.img lenovo-firmware.iso
1907 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
1908 </pre
></blockquote
>
1910 <p
>This USB stick booted the firmware upgrader just fine, and in a few
1911 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
1916 <title>Run your industrial metal working machine using Debian?
</title>
1917 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
1918 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
1919 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
1920 <description><p
>After many months of hard work by the good people involved in
1921 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
1922 system was accepted Sunday
1923 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
1924 Once it was available from Debian, I was surprised to discover from
1925 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
1926 popularity-contest numbers
</a
> that people have been reporting its use
1927 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
1928 be a good place to check out, but sadly is not working when visiting
1931 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
1932 Wikipedia quote is in place?
</p
>
1935 "LinuxCNC is a software system for numerical control of
1936 machines such as milling machines, lathes, plasma cutters, routers,
1937 cutting machines, robots and hexapods. It can control up to
9 axes or
1938 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
1939 several GUIs suited to specific kinds of usage (touch screen,
1940 interactive development).
"
1943 <p
>It can even control
3D printers. And even though the Wikipedia
1944 page indicate that it can only work with hard real time kernel
1945 features, it can also work with the user space soft real time features
1946 provided by the Debian kernel.
1947 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
1948 available from Github. The last few months I
've been involved in the
1949 translation setup for the program and documentation. Translators are
1951 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
1952 effort
</a
> using Weblate.
</p
>
1954 <p
>As usual, if you use Bitcoin and want to show your support of my
1955 activities, please send Bitcoin donations to my address
1956 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1961 <title>Debian still an excellent choice for Lego builders
</title>
1962 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
1963 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
1964 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
1965 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
1966 the packages under the team umbrella has been updated to fix
1967 packaging, lintian issues and BTS reports. In addition, a new and
1968 inspiring team member appeared on both the
1969 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
1970 Team mailing list
</a
> and
1971 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
1972 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
1973 Mindstorms programming, check out the
1974 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
1975 see what Debian can offer the Lego enthusiast.
</p
>
1977 <p
>Patches has been sent upstream, causing new upstream releases, one
1978 even the first one in more than ten years, and old upstreams was
1979 released with new ones. There are still a lot of work left, and the
1980 team welcome more members to help us make sure Debian is the Linux
1981 distribution of choice for Lego builders. If you want to contribute,
1982 join us in the IRC channel and become part of
1983 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
1984 Salsa
</a
>.
</p
>
1986 <p
>As usual, if you use Bitcoin and want to show your support of my
1987 activities, please send Bitcoin donations to my address
1988 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1993 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
1994 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
1995 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
1996 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
1997 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
1998 Debian Administrator
's Handbook
</a
> is available in six languages now.
1999 I am not sure which one of these are completely proof read, but the
2000 complete book is available in these languages:
2004 <li
>English
</li
>
2005 <li
>Norwegian Bokmål
</li
>
2006 <li
>German
</li
>
2007 <li
>Indonesian
</li
>
2008 <li
>Brazil Portuguese
</li
>
2009 <li
>Spanish
</li
>
2013 <p
>This is the list of languages more than
70% complete, in other
2014 words with not too much left to do:
</p
>
2018 <li
>Chinese (Simplified) -
90%
</li
>
2019 <li
>French -
79%
</li
>
2020 <li
>Italian -
79%
</li
>
2021 <li
>Japanese -
77%
</li
>
2022 <li
>Arabic (Morocco) -
75%
</li
>
2023 <li
>Persian -
71%
</li
>
2027 <p
>I wonder how long it will take to bring these to
100%.
</p
>
2029 <p
>Then there is the list of languages about halfway done:
</p
>
2033 <li
>Russian -
63%
</li
>
2034 <li
>Swedish -
53%
</li
>
2035 <li
>Chinese (Traditional) -
46%
</li
>
2036 <li
>Catalan -
45%
</li
>
2040 <p
>Several are on to a good start:
</p
>
2044 <li
>Dutch -
26%
</li
>
2045 <li
>Vietnamese -
25%
</li
>
2046 <li
>Polish -
23%
</li
>
2047 <li
>Czech -
22%
</li
>
2048 <li
>Turkish -
18%
</li
>
2052 <p
>Finally, there are the ones just getting started:
</p
>
2056 <li
>Korean -
4%
</li
>
2057 <li
>Croatian -
2%
</li
>
2058 <li
>Greek -
2%
</li
>
2059 <li
>Danish -
1%
</li
>
2060 <li
>Romanian -
1%
</li
>
2064 <p
>If you want to help provide a Debian instruction book in your own
2066 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
2067 to contribute to the translations.
</p
>
2069 <p
>As usual, if you use Bitcoin and want to show your support of my
2070 activities, please send Bitcoin donations to my address
2071 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2076 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
2077 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
2078 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
2079 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
2080 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
2081 others, the decentralized communication platform
2082 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
2083 (earlier known as Ring), managed to get
2084 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
2085 into Debian Testing. Several of its dependencies has caused build and
2086 propagation problems, which all seem to be solved now.
</p
>
2088 <p
>In addition to the fact that Jami is decentralized, similar to how
2089 bittorrent is decentralized, I first of all like how it is not
2090 connected to external IDs like phone numbers. This allow me to set up
2091 computers to send me notifications using Jami without having to find
2092 get a phone number for each computer. Automatic notification via Jami
2093 is also made trivial thanks to the provided client side API (as a DBus
2094 service). Here is my bourne shell script demonstrating how to let any
2095 system send a message to any Jami address. It will create a new
2096 identity before sending the message, if no Jami identity exist
2099 <p
><pre
>
2102 # Usage: $
0 <jami-address
> <message
>
2104 # Send
<message
> to
<jami-address
>, create local jami account if
2107 # License: GPL v2 or later at your choice
2108 # Author: Petter Reinholdtsen
2111 if [ -z
"$HOME
" ] ; then
2112 echo
"error: missing \$HOME, required for dbus to work
"
2116 # First, get dbus running if not already running
2117 DBUSLAUNCH=/usr/bin/dbus-launch
2118 PIDFILE=/run/asterisk/dbus-session.pid
2119 if [ -e $PIDFILE ] ; then
2121 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
2122 unset DBUS_SESSION_BUS_ADDRESS
2125 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
2126 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
2127 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
2128 DBUS_SESSION_BUS_PID=$!
2130 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
2131 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
2132 echo export DBUS_SESSION_BUS_ADDRESS
2138 part=
"$
1"; shift
2139 op=
"$
1"; shift
2140 dbus-send --session \
2141 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
2145 part=
"$
1"; shift
2146 op=
"$
1"; shift
2147 dbus-send --session --print-reply \
2148 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
2152 dringopreply ConfigurationManager getAccountList | \
2153 grep string | awk -F
'"' '{print $
2}
' | head -n
1
2156 account=$(firstaccount)
2158 if [ -z
"$account
" ] ; then
2159 echo
"Missing local account, trying to create it
"
2160 dringop ConfigurationManager addAccount \
2161 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
2162 account=$(firstaccount)
2163 if [ -z
"$account
" ] ; then
2164 echo
"unable to create local account
"
2169 # Not using dringopreply to ensure $
2 can contain spaces
2170 dbus-send --print-reply --session \
2171 --dest=cx.ring.Ring \
2172 /cx/ring/Ring/ConfigurationManager \
2173 cx.ring.Ring.ConfigurationManager.sendTextMessage \
2174 string:
"$account
" string:
"$
1" \
2175 dict:string:string:
"text/plain
",
"$
2"
2176 </pre
></p
>
2178 <p
>If you want to check it out yourself, visit the
2179 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
2180 more, and install the latest Jami client from Debian Unstable or
2183 <p
>As usual, if you use Bitcoin and want to show your support of my
2184 activities, please send Bitcoin donations to my address
2185 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2190 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
2191 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
2192 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
2193 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
2194 <description><p align=
"center
"><img align=
"center
" src=
"https://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
2196 <p
>I am happy to report that we finally made it! Norwegian Bokmål
2197 became the first translation published on paper of the new Buster
2198 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
2199 Administrator
's Handbook
</a
>". The print proof reading copy arrived
2200 some days ago, and it looked good, so now the book is approved for
2201 general distribution. This updated paperback edition
<a
2202 href=
"https://debian-handbook.info/get/#norwegian
">is available from
2203 lulu.com
</a
>. The book is also available for download in electronic
2204 form as PDF, EPUB and Mobipocket, and can also be
2205 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
2207 <p
>I am very happy to wrap up this Creative Common licensed project,
2208 which concludes several months of work by several volunteers. The
2209 number of Linux related books published in Norwegian are few, and I
2210 really hope this one will gain many readers, as it is packed with deep
2211 knowledge on Linux and the Debian ecosystem. The book will be
2212 available for various Internet book stores like Amazon and Barnes
&
2213 Noble soon, but I recommend buying
2214 "<a href=
"https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
9j7qwq.html
">Håndbok
2215 for Debian-administratoren
</a
>" directly from the source at Lulu.
2217 <p
>As usual, if you use Bitcoin and want to show your support of my
2218 activities, please send Bitcoin donations to my address
2219 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2224 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
2225 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
2226 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</guid>
2227 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
2228 <description><p
>Thanks to the good work of several volunteers, the updated edition
2229 of the Norwegian translation for
2230 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2231 Handbook
</a
>" is now almost completed. After many months of proof
2232 reading, I consider the proof reading complete enough for us to move
2233 to the next step, and have asked for the print version to be prepared
2234 and sent of to the print on demand service lulu.com. While it is
2235 still not to late if you find any incorrect translations on
2236 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
2237 hosted Weblate service
</a
>, but it will be soon. :) You can check out
2238 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
2239 edition on the web
</a
> until the print edition is ready.
</p
>
2241 <p
>The book will be for sale on lulu.com and various web book stores,
2242 with links available from the web site for the book linked to above.
2243 I hope a lot of readers find it useful.
</p
>
2245 <p
>As usual, if you use Bitcoin and want to show your support of my
2246 activities, please send Bitcoin donations to my address
2247 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2252 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
2253 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
2254 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
2255 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
2256 <description><p
>Three years ago, the first Norwegian Bokmål edition of
2257 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2258 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
2259 new and updated version based on Buster is getting ready. Work on the
2260 updated Norwegian Bokmål edition has been going on for a few months
2261 now, and yesterday, we reached the first mile stone, with
100% of the
2262 texts being translated. A lot of proof reading remains, of course,
2263 but a major step towards a new edition has been taken.
</p
>
2265 <p
>The book is translated by volunteers, and we would love to get some
2266 help with the proof reading. The translation uses
2267 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
2268 hosted Weblate service
</a
>, and we welcome everyone to have a look and
2269 submit improvements and suggestions. There is also a proof readers
2270 PDF available on request, get in touch if you want to help out that
2273 <p
>As usual, if you use Bitcoin and want to show your support of my
2274 activities, please send Bitcoin donations to my address
2275 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2280 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
2281 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
2282 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
2283 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
2284 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
2285 User Group
</a
>, I have the pleasure of receiving the
2286 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
2287 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
2288 several times a year. I rarely have time to read all the articles,
2289 but try to at least skim through them all as there is a lot of nice
2290 knowledge passed on there. I even carry the latest issue with me most
2291 of the time to try to get through all the articles when I have a few
2292 spare minutes.
</p
>
2294 <p
>The other day I came across a nice article titled
2295 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
2296 Secure Socket API: TLS as an Operating System Service
</a
>" with a
2297 marvellous idea I hope can make it all the way into the POSIX standard.
2298 The idea is as simple as it is powerful. By introducing a new
2299 socket() option IPPROTO_TLS to use TLS, and a system wide service to
2300 handle setting up TLS connections, one both make it trivial to add TLS
2301 support to any program currently using the POSIX socket API, and gain
2302 system wide control over certificates, TLS versions and encryption
2303 systems used. Instead of doing this:
</p
>
2305 <p
><blockquote
><pre
>
2306 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
2307 </pre
></blockquote
></p
>
2309 <p
>the program code would be doing this:
<p
>
2311 <p
><blockquote
><pre
>
2312 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
2313 </pre
></blockquote
></p
>
2315 <p
>According to the ;login: article, converting a C program to use TLS
2316 would normally modify only
5-
10 lines in the code, which is amazing
2317 when compared to using for example the OpenSSL API.
</p
>
2319 <p
>The project has set up the
2320 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
2321 web site to spread the idea, and the code for a kernel module and the
2322 associated system daemon is available from two github repositories:
2323 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
2324 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
2325 Unfortunately there is no explicit license information with the code,
2326 so its copyright status is unclear. A
2327 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
2328 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
2330 <p
>I love the idea of extending socket() to gain TLS support, and
2331 understand why it is an advantage to implement this as a kernel module
2332 and system wide service daemon, but can not help to think that it
2333 would be a lot easier to get projects to move to this way of setting
2334 up TLS if it was done with a user space approach where programs
2335 wanting to use this API approach could just link with a wrapper
2338 <p
>I recommend you check out this simple and powerful approach to more
2339 secure network connections. :)
</p
>
2341 <p
>As usual, if you use Bitcoin and want to show your support of my
2342 activities, please send Bitcoin donations to my address
2343 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2348 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
2349 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
2350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
2351 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
2352 <description><p
>Half a year ago,
2353 <a href=
"https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
2354 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
2355 client
</a
>, capable of peer-to-peer encrypted communication. It
2356 handle both messages, audio and video. It uses distributed hash
2357 tables instead of central infrastructure to connect its users to each
2358 other, which in my book is a plus. I mentioned briefly that it could
2359 also work as a SIP client, which came in handy when the higher
2360 educational sector in Norway started to promote Zoom as its video
2361 conferencing solution. I am reluctant to use the official Zoom client
2362 software, due to their
<a href=
"https://zoom.us/terms
">copyright
2363 license clauses
</a
> prohibiting users to reverse engineer (for example
2364 to check the security) and benchmark it, and thus prefer to connect to
2365 Zoom meetings with free software clients.
</p
>
2367 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
2368 password set on the room. The Jami daemon leak memory like crazy
2369 (approximately
1 GiB a minute) when I am connected to the video
2370 conference, so I had to restart the client every
7-
10 minutes, which
2371 is not great. I tried to get other SIP Linux clients to work
2372 without success, so I decided I would have to live with this wart
2373 until someone managed to fix the leak in the dring code base. But
2374 another problem showed up once the rooms were password protected. I
2375 could not get my dial tone signaling through from Jami to Zoom, and
2376 dial tone signaling is used to enter the password when connecting to
2377 Zoom. I tried a lot of different permutations with my Jami and
2378 Asterisk setup to try to figure out why the signaling did not get
2379 through, only to finally discover that the fundamental problem seem to
2380 be that Zoom is simply not able to receive dial tone signaling when
2381 connecting via SIP. There seem to be nothing wrong with the Jami and
2382 Asterisk end, it is simply broken in the Zoom end. I got help from a
2383 very skilled VoIP engineer figuring out this last part. And being a
2384 very skilled engineer, he was also able to locate a solution for me.
2385 Or to be exact, a workaround that solve my initial problem of
2386 connecting to password protected Zoom rooms using Jami.
</p
>
2388 <p
>So, how do you do this, I am sure you are wondering by now. The
2390 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
2391 from Zoom
</a
>, and it is to modify the SIP address to include the room
2392 password. What is most surprising about this is that the
2393 automatically generated email from Zoom with instructions on how to
2394 connect via SIP do not mention this. The SIP address to use normally
2395 consist of the room ID (a number), an @ character and the IP address
2396 of the Zoom SIP gateway. But Zoom understand a lot more than just the
2397 room ID in front of the at sign. The format is
"<tt
>[Meeting
2398 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
2399 can both enter password, control the layout (full screen, active
2400 presence and gallery) and specify the host key to start the meeting.
2401 The full SIP address entered into Jami to provide the password will
2402 then look like this (all using made up numbers):
</p
>
2404 <p
><blockquote
>
2405 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
2406 </blockquote
></p
>
2408 <p
>Now if only jami would reduce its memory usage, I could even
2409 recommend this setup to others. :)
</p
>
2411 <p
>As usual, if you use Bitcoin and want to show your support of my
2412 activities, please send Bitcoin donations to my address
2413 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2418 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
2419 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
2420 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
2421 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
2422 <description><p
>The curiosity got the better of me when
2423 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
2424 reported
</a
> that New Jersey was desperately looking for
2425 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
2426 and a few days later it was reported that
2427 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
2428 tried to locate COBOL programmers
</a
>.
</p
>
2430 <p
>I thus decided to have a look at free software alternatives to
2431 learn COBOL, and had the pleasure to find
2432 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
2433 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
2434 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
2435 transforming COBOL code to C or C++ before giving it to GCC or Visual
2436 Studio to build binaries.
</p
>
2438 <p
>I managed to get in touch with upstream, and was impressed with the
2439 quick response, and also was happy to see a new Debian maintainer
2440 taking over when the original one recently asked to be replaced. A
2441 new Debian upload was done as recently as yesterday.
</p
>
2443 <p
>Using the Debian package, I was able to follow a simple COBOL
2444 introduction and make and run simple COBOL programs. It was fun to
2445 learn a new programming language. If you want to test for yourself,
2446 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
2447 page
</a
> have a few simple examples to get you startet.
</p
>
2449 <p
>As I do not have much experience with COBOL, I do not know how
2450 standard compliant it is, but it claim to pass most tests from COBOL
2451 test suite, which sound good to me. It is nice to know it is possible
2452 to learn COBOL using software without any usage restrictions, and I am
2453 very happy such nice free software project as this is available. If
2454 you as me is curious about COBOL, check it out.
</p
>
2456 <p
>As usual, if you use Bitcoin and want to show your support of my
2457 activities, please send Bitcoin donations to my address
2458 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2463 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
2464 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
2465 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
2466 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
2467 <description><p
>Some years ago, in
2016, I
2468 <a href=
"https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
2469 for the first time about
</a
> the Ring peer to peer messaging system.
2470 It would provide messaging without any central server coordinating the
2471 system and without requiring all users to register a phone number or
2472 own a mobile phone. Back then, I could not get it to work, and put it
2473 aside until it had seen more development. A few days ago I decided to
2474 give it another try, and am happy to report that this time I am able
2475 to not only send and receive messages, but also place audio and video
2476 calls. But only if UDP is not blocked into your network.
</p
>
2478 <p
>The Ring system changed name earlier this year to
2479 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
2480 tried doing web search for
'ring
' when I discovered it for the first
2481 time, and can only applaud this change as it is impossible to find
2482 something called Ring among the noise of other uses of that word. Now
2483 you can search for
'jami
' and this client and
2484 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
2485 least on duckduckgo.
</p
>
2487 <p
>Jami will by default encrypt messages as well as audio and video
2488 calls, and try to send them directly between the communicating parties
2489 if possible. If this proves impossible (for example if both ends are
2490 behind NAT), it will use a central SIP TURN server maintained by the
2491 Jami project. Jami can also be a normal SIP client. If the SIP
2492 server is unencrypted, the audio and video calls will also be
2493 unencrypted. This is as far as I know the only case where Jami will
2494 do anything without encryption.
</p
>
2496 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
2497 Android, iOS, and Android TV. It is included in Debian already. Jami
2498 also work for those using F-Droid without any Google connections,
2499 while Signal do not.
2500 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
2501 protocol
</a
> is described in the Ring project wiki. The system uses a
2502 distributed hash table (DHT) system (similar to BitTorrent) running
2503 over UDP. On one of the networks I use, I discovered Jami failed to
2504 work. I tracked this down to the fact that incoming UDP packages
2505 going to ports
1-
49999 were blocked, and the DHT would pick a random
2506 port and end up in the low range most of the time. After talking to
2507 the developers, I solved this by enabling the dhtproxy in the
2508 settings, thus using TCP to talk to a central DHT proxy instead of
2510 peering directly with others. I
've been told the developers are
2511 working on allowing DHT to use TCP to avoid this problem. I also ran
2512 into a problem when trying to talk to the version of Ring included in
2513 Debian Stable (Stretch). Apparently the protocol changed between
2514 beta2 and the current version, making these clients incompatible.
2515 Hopefully the protocol will not be made incompatible in the
2518 <p
>It is worth noting that while looking at Jami and its features, I
2519 came across another communication platform I have not tested yet. The
2520 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
2521 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
2522 become the topic of a future blog post.
</p
>
2524 <p
>As usual, if you use Bitcoin and want to show your support of my
2525 activities, please send Bitcoin donations to my address
2526 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2531 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
2532 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
2533 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
2534 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
2535 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
2536 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
2537 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
2538 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
2539 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
2540 nye versjonen kom på nyåret, og ble
2541 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
2542 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
2543 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
2544 måtte justeres, men ikke noe alvorlig. Har oppdatert
2545 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
2546 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
2548 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
2549 å spille for oss som liker slikt. :)
</p
>
2551 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
2552 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
2554 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
2555 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
2560 <title>Debian now got everything you need to program Micro:bit
</title>
2561 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
2562 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
2563 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
2564 <description><p
>I am amazed and very pleased to discover that since a few days ago,
2565 everything you need to program the
<a href=
"https://microbit.org/
">BBC
2566 micro:bit
</a
> is available from the Debian archive. All this is
2567 thanks to the hard work of Nick Morrott and the Debian python
2568 packaging team. The micro:bit project recommend the mu-editor to
2569 program the microcomputer, as this editor will take care of all the
2570 machinery required to injekt/flash micropython alongside the program
2571 into the micro:bit, as long as the pieces are available.
</p
>
2573 <p
>There are three main pieces involved. The first to enter Debian
2575 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
2576 which was accepted into the archive
2019-
01-
12. The next one was
2577 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
2578 showed up
2019-
01-
13. The final and hardest part to to into the
2580 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
2581 which needed to get its build system and dependencies into Debian
2582 before it was accepted
2019-
01-
20. The last one is already in Debian
2583 Unstable and should enter Debian Testing / Buster in three days. This
2584 all allow any user of the micro:bit to get going by simply running
2585 'apt install mu-editor
' when using Testing or Unstable, and once
2586 Buster is released as stable, all the users of Debian stable will be
2587 catered for.
</p
>
2589 <p
>As a minor final touch, I added rules to
2590 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
2591 package
</a
> for recognizing micro:bit and recommend the mu-editor
2592 package. This make sure any user of the isenkram desktop daemon will
2593 get a popup suggesting to install mu-editor then the USB cable from
2594 the micro:bit is inserted for the first time.
</p
>
2596 <p
>This should make it easier to have fun.
</p
>
2598 <p
>As usual, if you use Bitcoin and want to show your support of my
2599 activities, please send Bitcoin donations to my address
2600 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2605 <title>Learn to program with Minetest on Debian
</title>
2606 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
2607 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
2608 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
2609 <description><p
>A fun way to learn how to program
2610 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
2611 instructions in the book
2612 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
2613 with Minecraft
</a
>", which introduces programming in Python to people
2614 who like to play with Minecraft. The book uses a Python library to
2615 talk to a TCP/IP socket with an API accepting build instructions and
2616 providing information about the current players in a Minecraft world.
2617 The TCP/IP API was first created for the Minecraft implementation for
2618 Raspberry Pi, and has since been ported to some server versions of
2619 Minecraft. The book contain recipes for those using Windows, MacOSX
2620 and Raspian. But a little known fact is that you can follow the same
2621 recipes using the free software construction game
2622 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
2624 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
2625 Minetest module implementing the same API
</a
>, making it possible to
2626 use the Python programs coded to talk to Minecraft with Minetest too.
2628 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
2629 this module
</a
> to Debian two weeks ago, and as soon as it clears the
2630 FTP masters NEW queue, learning to program Python with Minetest on
2631 Debian will be a simple
'apt install
' away. The Debian package is
2632 maintained as part of the Debian Games team, and
2633 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
2634 packaging rules
</a
> are currently located under
'unfinished
' on
2637 <p
>You will most likely need to install several of the Minetest
2638 modules in Debian for the examples included with the library to work
2639 well, as there are several blocks used by the example scripts that are
2640 provided via modules in Minetest. Without the required blocks, a
2641 simple stone block is used instead. My initial testing with a analog
2642 clock did not get gold arms as instructed in the python library, but
2643 instead used stone arms.
</p
>
2645 <p
>I tried to find a way to add the API to the desktop version of
2646 Minecraft, but were unable to find any working recipes. The
2647 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
2648 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
2649 working with a standalone Minecraft server setup. Are there any
2650 options to use with the normal desktop version?
</p
>
2652 <p
>As usual, if you use Bitcoin and want to show your support of my
2653 activities, please send Bitcoin donations to my address
2654 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2659 <title>Time for an official MIME type for patches?
</title>
2660 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
2661 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
2662 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
2663 <description><p
>As part of my involvement in
2664 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
2665 archive API project
</a
>, I
've been importing a fairly large lump of
2666 emails into a test instance of the archive to see how well this would
2667 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
2668 notmuch email database
</a
>, all public emails sent to me via
2669 @lists.debian.org, giving me a set of around
216 000 emails to import.
2670 In the process, I had a look at the various attachments included in
2671 these emails, to figure out what to do with attachments, and noticed
2672 that one of the most common attachment formats do not have
2673 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
2674 official MIME type
</a
> registered with IANA/IETF. The output from
2675 diff, ie the input for patch, is on the top
10 list of formats
2676 included in these emails. At the moment people seem to use either
2677 text/x-patch or text/x-diff, but neither is officially registered. It
2678 would be better if one official MIME type were registered and used
2679 everywhere.
</p
>
2681 <p
>To try to get one official MIME type for these files, I
've brought
2683 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
2684 media-types mailing list
</a
>. If you are interested in discussion
2685 which MIME type to use as the official for patch files, or involved in
2686 making software using a MIME type for patches, perhaps you would like
2687 to join the discussion?
</p
>
2689 <p
>As usual, if you use Bitcoin and want to show your support of my
2690 activities, please send Bitcoin donations to my address
2691 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2696 <title>Automatic Google Drive sync using grive in Debian
</title>
2697 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
2698 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
2699 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
2700 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
2701 rescue the remains, I helped set up automatic sync with Google Drive.
2702 I did not find any sensible Debian package handling this
2703 automatically, so I rebuild the grive2 source from
2704 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
2705 task and added a autostart desktop entry and a small shell script to
2706 run in the background while the user is logged in to do the sync.
2707 Here is a sketch of the setup for future reference.
</p
>
2709 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
2710 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
2711 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
2712 to start the sync when the user log in:
</p
>
2714 <p
><blockquote
><pre
>
2716 Name=Google drive autosync
2718 Exec=/home/user/bin/grive-sync
2719 </pre
></blockquote
></p
>
2721 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
2722 ~/googledrive/ with the files in Google Drive.
</p
>
2724 <p
><blockquote
><pre
>
2729 if [
"$syncpid
" ] ; then
2733 trap cleanup EXIT INT QUIT
2734 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
2737 if ! xhost
>/dev/null
2>&1 ; then
2738 echo
"no DISPLAY, exiting as the user probably logged out
"
2741 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
2742 /usr/lib/grive/grive-sync.sh sync googledrive
2745 done
2>&1 | sed
"s%^%$
0:%
"
2746 </pre
></blockquote
></p
>
2748 <p
>Feel free to use the setup if you want. It can be assumed to be
2749 GNU GPL v2 licensed (or any later version, at your leisure), but I
2750 doubt this code is possible to claim copyright on.
</p
>
2752 <p
>As usual, if you use Bitcoin and want to show your support of my
2753 activities, please send Bitcoin donations to my address
2754 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2759 <title>Using the Kodi API to play Youtube videos
</title>
2760 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
2761 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
2762 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
2763 <description><p
>I continue to explore my Kodi installation, and today I wanted to
2764 tell it to play a youtube URL I received in a chat, without having to
2765 insert search terms using the on-screen keyboard. After searching the
2766 web for API access to the Youtube plugin and testing a bit, I managed
2767 to find a recipe that worked. If you got a kodi instance with its API
2768 available from http://kodihost/jsonrpc, you can try the following to
2769 have check out a nice cover band.
</p
>
2771 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
2772 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
2773 "params
": {
"item
": {
"file
":
2774 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
2775 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
2777 <p
>I
've extended kodi-stream program to take a video source as its
2778 first argument. It can now handle direct video links, youtube links
2779 and
'desktop
' to stream my desktop to Kodi. It is almost like a
2780 Chromecast. :)
</p
>
2782 <p
>As usual, if you use Bitcoin and want to show your support of my
2783 activities, please send Bitcoin donations to my address
2784 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2789 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
2790 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
2791 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
2792 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
2793 <description><p
>For a while now, I have looked for a sensible way to share images
2794 with my family using a self hosted solution, as it is unacceptable to
2795 place images from my personal life under the control of strangers
2796 working for data hoarders like Google or Dropbox. The last few days I
2797 have drafted an approach that might work out, and I would like to
2798 share it with you. I would like to publish images on a server under
2799 my control, and point some Internet connected display units using some
2800 free and open standard to the images I published. As my primary
2801 language is not limited to ASCII, I need to store metadata using
2802 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
2803 of reading a RSS feed with image references (aka using the
2804 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
2805 of such frames. In the end I gave up that approach.
</p
>
2807 <p
>Some months ago, I discovered that
2808 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
2809 read images from a RSS feed, and used it to set up a screen saver on
2810 my home info screen, showing images from the Daily images feed from
2811 NASA. This proved to work well. More recently I discovered that
2812 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
2813 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
2814 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
2815 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
2816 screen saver capable of reading a RSS feed with images and news. For
2817 fun, I used it this summer to test Kodi on my parents TV by hooking up
2818 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
2819 screen saver showing selected pictures from my selection.
</p
>
2821 <p
>Armed with motivation and a test photo frame, I set out to generate
2822 a RSS feed for the Kodi instance. I adjusted my
<a
2823 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
2824 /var/www/html/privatepictures/, wrote a small Perl script to extract
2825 title and description metadata from the photo files and generate the
2826 RSS file. I ended up using Perl instead of python, as the
2827 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
2828 tags I ended up using, while python3-exif did not. The relevant EXIF
2829 tags only support ASCII, so I had to find better alternatives. XMP
2830 seem to have the support I need.
</p
>
2832 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
2833 use tags that can be easily added/updated using normal free software
2834 photo managing software. I ended up using the tags set using this
2835 exiftool command, as these tags can also be set using digiKam:
</p
>
2837 <blockquote
><pre
>
2838 exiftool -headline=
'The RSS image title
' \
2839 -description=
'The RSS image description.
' \
2840 -subject+=for-family photo.jpeg
2841 </pre
></blockquote
>
2843 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
2844 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
2845 use the keyword/subject
'for-family
' to flag that the photo should be
2846 shared with my family. Images with this keyword set are located and
2847 copied into my Freedombox for the RSS generating script to find.
</p
>
2849 <p
>Are there better ways to do this? Get in touch if you have better
2850 suggestions.
</p
>
2852 <p
>As usual, if you use Bitcoin and want to show your support of my
2853 activities, please send Bitcoin donations to my address
2854 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2859 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
2860 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
2861 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
2862 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
2863 <description><p
>Last night, I wrote
2864 <a href=
"https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
2865 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
2866 During the day I received valuable feedback, and thanks to the
2867 suggestions I have been able to rewrite the recipe into a much simpler
2868 approach requiring no setup at all. It is a single script that take
2869 care of it all.
</p
>
2871 <p
>This new script uses GStreamer instead of VLC to capture the
2872 desktop and stream it to Kodi. This fixed the video quality issue I
2873 saw initially. It further removes the need to add a m3u file on the
2874 Kodi machine, as it instead connects to
2875 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
2876 Kodi
</a
> and simply ask Kodi to play from the stream created using
2877 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
2878 the script below, run it with the DNS name or IP address of the kodi
2879 server to stream to as the only argument, and watch your screen show
2880 up on the Kodi screen. Note, it depend on multicast on the local
2881 network, so if you need to stream outside the local network, the
2882 script must be modified. Also note, I have no idea if audio work, as
2883 I only care about the picture part.
</p
>
2885 <blockquote
><pre
>
2888 # Stream the Linux desktop view to Kodi. See
2889 # https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
2890 # for backgorund information.
2892 # Make sure the stream is stopped in Kodi and the gstreamer process is
2893 # killed if something go wrong (for example if curl is unable to find the
2894 # kodi server). Do the same when interrupting this script.
2898 params=
"$
3"
2899 curl --silent --header
'Content-Type: application/json
' \
2900 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
2901 "http://$host/jsonrpc
"
2904 if [ -n
"$kodihost
" ] ; then
2905 # Stop the playing when we end
2906 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
2907 jq .result[].playerid)
2908 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
2910 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
2911 kill
"$gstpid
"
2914 trap cleanup EXIT INT
2916 if [ -n
"$
1" ]; then
2927 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
2928 cut -d
" " -f2|head -
1)
2929 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
2930 videoconvert ! queue2 ! \
2931 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
2932 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
2933 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
2934 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
2935 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
2936 > /dev/null
2>&1 &
2939 # Give stream a second to get going
2942 # Ask kodi to start streaming using its JSON-RPC API
2943 kodicmd
"$kodihost
" Player.Open \
2944 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
2946 # wait for gst to end
2947 wait
"$gstpid
"
2948 </pre
></blockquote
>
2950 <p
>I hope you find the approach useful. I know I do.
</p
>
2952 <p
>As usual, if you use Bitcoin and want to show your support of my
2953 activities, please send Bitcoin donations to my address
2954 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2959 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
2960 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
2961 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
2962 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
2963 <description><p
>PS: See
2964 <ahref=
"https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
2965 followup post
</a
> for a even better approach.
</p
>
2967 <p
>A while back, I was asked by a friend how to stream the desktop to
2968 my projector connected to Kodi. I sadly had to admit that I had no
2969 idea, as it was a task I never had tried. Since then, I have been
2970 looking for a way to do so, preferable without much extra software to
2971 install on either side. Today I found a way that seem to kind of
2972 work. Not great, but it is a start.
</p
>
2974 <p
>I had a look at several approaches, for example
2975 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
2976 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
2977 local storage enough to store the stream locally. This is not going
2978 to work well for me, lacking enough free space, and it would
2979 impossible for my friend to get working.
</p
>
2981 <p
>Next, it occurred to me that perhaps I could use VLC to create a
2982 video stream that Kodi could play. Preferably using
2983 broadcast/multicast, to avoid having to change any setup on the Kodi
2984 side when starting such stream. Unfortunately, the only recipe I
2985 could find using multicast used the rtp protocol, and this protocol
2986 seem to not be supported by Kodi.
</p
>
2988 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
2989 have to specify the IP address of the streaming machine in both the
2990 sending command and the file on the Kodi server. But it is showing my
2991 desktop, and thus allow us to have a shared look on the big screen at
2992 the programs I work on.
</p
>
2994 <p
>I did not spend much time investigating codeces. I combined the
2995 rtp and rtsp recipes from
2996 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
2997 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
2998 this working on the desktop/streaming end.
</p
>
3000 <blockquote
><pre
>
3001 vlc screen:// --sout \
3002 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
3003 </pre
></blockquote
>
3005 <p
>I ssh-ed into my Kodi box and created a file like this with the
3006 same IP address:
</p
>
3008 <blockquote
><pre
>
3009 echo rtsp://
192.168.11.4:
8080/test.sdp \
3010 > /storage/videos/screenstream.m3u
3011 </pre
></blockquote
>
3013 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
3014 as I can tell the IP must be hardcoded for this to work. In other
3015 words, if someone elses machine is going to do the steaming, you have
3016 to update screenstream.m3u on the Kodi machine and adjust the vlc
3017 recipe. To get started, locate the file in Kodi and select the m3u
3018 file while the VLC stream is running. The desktop then show up in my
3019 big screen. :)
</p
>
3021 <p
>When using the same technique to stream a video file with audio,
3022 the audio quality is really bad. No idea if the problem is package
3023 loss or bad parameters for the transcode. I do not know VLC nor Kodi
3024 enough to tell.
</p
>
3026 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
3027 succestions and reminded me about an important step. The
"screen:
"
3028 input source is only available once the vlc-plugin-access-extra
3029 package is installed on Debian. Without it, you will see this error
3030 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
3031 for details.
" He further found that it is possible to drop some parts
3032 of the VLC command line to reduce the amount of hardcoded information.
3033 It is also useful to consider using cvlc to avoid having the VLC
3034 window in the desktop view. In sum, this give us this command line on
3037 <blockquote
><pre
>
3038 cvlc screen:// --sout \
3039 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
3040 </pre
></blockquote
>
3042 <p
>and this on the Kodi end
<p
>
3044 <blockquote
><pre
>
3045 echo rtsp://
192.168.11.4:
8080/ \
3046 > /storage/videos/screenstream.m3u
3047 </pre
></blockquote
>
3049 <p
>Still bad image quality, though. But I did discover that streaming
3050 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
3051 audio quality, so I guess the issue is in the input or transcoding
3052 parts, not the rtsp part. I
've tried to change the vb and ab
3053 parameters to use more bandwidth, but it did not make a
3054 difference.
</p
>
3056 <p
>I further received a suggestion from Einar Haraldseid to try using
3057 gstreamer instead of VLC, and this proved to work great! He also
3058 provided me with the trick to get Kodi to use a multicast stream as
3059 its source. By using this monstrous oneliner, I can stream my desktop
3060 with good video quality in reasonable framerate to the
239.255.0.1
3061 multicast address on port
1234:
3063 <blockquote
><pre
>
3064 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
3065 videoconvert ! queue2 ! \
3066 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
3067 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
3068 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
3069 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
3070 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
3071 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
3072 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
3073 </pre
></blockquote
>
3075 <p
>and this on the Kodi end
<p
>
3077 <blockquote
><pre
>
3078 echo udp://@
239.255.0.1:
1234 \
3079 > /storage/videos/screenstream.m3u
3080 </pre
></blockquote
>
3082 <p
>Note the trick to pick a valid pulseaudio source. It might not
3083 pick the one you need. This approach will of course lead to trouble
3084 if more than one source uses the same multicast port and address.
3085 Note the ttl-mc=
1 setting, which limit the multicast packages to the
3086 local network. If the value is increased, your screen will be
3087 broadcasted further, one network
"hop
" for each increase (read up on
3088 multicast to learn more. :)!
</p
>
3090 <p
>Having cracked how to get Kodi to receive multicast streams, I
3091 could use this VLC command to stream to the same multicast address.
3092 The image quality is way better than the rtsp approach, but gstreamer
3093 seem to be doing a better job.
</p
>
3095 <blockquote
><pre
>
3096 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
3097 </pre
></blockquote
>
3099 <p
>As usual, if you use Bitcoin and want to show your support of my
3100 activities, please send Bitcoin donations to my address
3101 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3106 <title>What is the most supported MIME type in Debian in
2018?
</title>
3107 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
3108 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
3109 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
3110 <description><p
>Five years ago,
3111 <a href=
"https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
3112 measured what the most supported MIME type in Debian was
</a
>, by
3113 analysing the desktop files in all packages in the archive. Since
3114 then, the DEP-
11 AppStream system has been put into production, making
3115 the task a lot easier. This made me want to repeat the measurement,
3116 to see how much things changed. Here are the new numbers, for
3117 unstable only this time:
3119 <p
><strong
>Debian Unstable:
</strong
></p
>
3123 ----- -----------------------
3135 30 audio/x-vorbis+ogg
3136 29 image/x-portable-pixmap
3138 27 image/x-portable-bitmap
3140 26 application/x-ogg
3146 <p
>The list was created like this using a sid chroot:
"cat
3147 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
3148 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
3150 <p
>It is interesting to see how image formats have passed text/plain
3151 as the most announced supported MIME type. These days, thanks to the
3152 AppStream system, if you run into a file format you do not know, and
3153 want to figure out which packages support the format, you can find the
3154 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
3155 look up all packages announcing support for this format in their
3156 AppStream metadata (XML or .desktop file) using
"appstreamcli
3157 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
3158 me, want to know which packages support inode/directory, you can get a
3159 list like this:
</p
>
3161 <p
><blockquote
><pre
>
3162 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
3169 Package: doublecmd-common
3171 Package: enlightenment
3191 </pre
></blockquote
></p
>
3193 <p
>Using the same method, I can quickly discover that the Sketchup file
3194 format is not yet supported by any package in Debian:
</p
>
3196 <p
><blockquote
><pre
>
3197 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
3198 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
3200 </pre
></blockquote
></p
>
3202 <p
>Yesterday I used it to figure out which packages support the STL
3D
3205 <p
><blockquote
><pre
>
3206 % appstreamcli what-provides mimetype application/sla|grep Package
3211 </pre
></blockquote
></p
>
3213 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
3215 <p
>As usual, if you use Bitcoin and want to show your support of my
3216 activities, please send Bitcoin donations to my address
3217 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3222 <title>Debian APT upgrade without enough free space on the disk...
</title>
3223 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
3224 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
3225 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
3226 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
3227 for a while, and when I need to update it there is not enough free
3228 space on the disk for apt to do a normal
'apt upgrade
'. I normally
3229 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
3230 upgrade only some of the packages in one batch, until the amount of
3231 packages to download fall below the amount of free space available.
3232 Today, I had about
500 packages to upgrade, and after a while I got
3233 tired of trying to install chunks of packages manually. I concluded
3234 that I did not have the spare hours required to complete the task, and
3235 decided to see if I could automate it. I came up with this small
3236 script which I call
'apt-in-chunks
':
</p
>
3238 <p
><blockquote
><pre
>
3241 # Upgrade packages when the disk is too full to upgrade every
3242 # upgradable package in one lump. Fetching packages to upgrade using
3243 # apt, and then installing using dpkg, to avoid changing the package
3244 # flag for manual/automatic.
3249 if [
"$
1" ]; then
3250 grep -v
"$
1"
3256 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
3257 echo
"Upgrading $p
"
3259 apt install --download-only -y $p
3260 for f in /var/cache/apt/archives/*.deb; do
3261 if [ -e
"$f
" ]; then
3262 dpkg -i /var/cache/apt/archives/*.deb
3267 </pre
></blockquote
></p
>
3269 <p
>The script will extract the list of packages to upgrade, try to
3270 download the packages needed to upgrade one package, install the
3271 downloaded packages using dpkg. The idea is to upgrade packages
3272 without changing the APT mark for the package (ie the one recording of
3273 the package was manually requested or pulled in as a dependency). To
3274 use it, simply run it as root from the command line. If it fail, try
3275 'apt install -f
' to clean up the mess and run the script again. This
3276 might happen if the new packages conflict with one of the old
3277 packages. dpkg is unable to remove, while apt can do this.
</p
>
3279 <p
>It take one option, a package to ignore in the list of packages to
3280 upgrade. The option to ignore a package is there to be able to skip
3281 the packages that are simply too large to unpack. Today this was
3282 'ghc
', but I have run into other large packages causing similar
3283 problems earlier (like TeX).
</p
>
3285 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
3286 alternative ways to handle this. The
"unattended-upgrades
3287 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
3288 each package to upgrade, and then upgrade them in order, smallest set
3289 first. It might be a better option than my above mentioned script.
3290 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
3291 the need for using
"dpkg -i
" in the script above.
</p
>
3293 <p
>As usual, if you use Bitcoin and want to show your support of my
3294 activities, please send Bitcoin donations to my address
3295 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3300 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
3301 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
3302 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
3303 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
3304 <description><p
>A new version of the
3305 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
3306 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
3307 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
3308 useful. It was uploaded the last few days, and the last update will
3309 enter testing tomorrow. See the
3310 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
3311 notes
</a
> for the list of bug fixes and new features. Version
3.2
3312 was announced
6 days ago. We will try to get it into Debian as
3315 <p
>More information related to
3D printing is available on the
3316 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
3317 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
3318 in Debian.
</p
>
3320 <p
>As usual, if you use Bitcoin and want to show your support of my
3321 activities, please send Bitcoin donations to my address
3322 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3327 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
3328 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
3329 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
3330 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
3331 <description><p
>After several months of working and waiting, I am happy to report
3332 that the nice and user friendly
3D printer slicer software Cura just
3333 entered Debian Unstable. It consist of five packages,
3334 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
3335 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
3336 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
3337 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
3338 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
3339 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
3340 two, uranium and cura, entered Unstable yesterday. This should make
3341 it easier for Debian users to print on at least the Ultimaker class of
3342 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
3343 make life easier for at least me. :)
</p
>
3345 <p
>The work to make this happen was done by Gregor Riepl, and I was
3346 happy to assist him in sponsoring the packages. With the introduction
3347 of Cura, Debian is up to three
3D printer slicers at your service,
3348 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
3349 printer, give it a go. :)
</p
>
3351 <p
>The
3D printer software is maintained by the
3D printer Debian
3352 team, flocking together on the
3353 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
3354 mailing list and the
3355 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
3356 IRC channel.
</p
>
3358 <p
>The next step for Cura in Debian is to update the cura package to
3359 version
3.0.3 and then update the entire set of packages to version
3360 3.1.0 which showed up the last few days.
</p
>
3365 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
3366 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
3367 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
3368 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
3369 <description><p
>At my nearby maker space,
3370 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
3371 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
3372 on Windows and MacOS X than Linux, because the software involved had
3373 to be manually compiled and set up on Linux while premade packages
3374 worked out of the box on Windows and MacOS X. I found this annoying,
3375 as the software involved,
3376 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
3377 and should be trivial to get up and running on Linux if someone took
3378 the time to package it for the relevant distributions. I even found
3379 <a href=
"https://bugs.debian.org/
706656">a request for adding into
3380 Debian
</a
> from
2013, which had seem some activity over the years but
3381 never resulted in the software showing up in Debian. So a few days
3382 ago I offered my help to try to improve the situation.
</p
>
3384 <p
>Now I am very happy to see that all the packages required by a
3385 working Cura in Debian are uploaded into Debian and waiting in the NEW
3386 queue for the ftpmasters to have a look. You can track the progress
3388 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
3389 status page for the
3D printer team
</a
>.
</p
>
3391 <p
>The uploaded packages are a bit behind upstream, and was uploaded
3392 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
3393 queue
</a
> while we work up updating the packages to the latest
3394 upstream version.
</p
>
3396 <p
>On a related note, two competitors for Cura, which I found harder
3397 to use and was unable to configure correctly for Ultimaker
2+ in the
3398 short time I spent on it, are already in Debian. If you are looking
3399 for
3D printer
"slicers
" and want something already available in
3401 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
3402 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
3403 The latter is a fork of the former.
</p
>
3405 <p
>As usual, if you use Bitcoin and want to show your support of my
3406 activities, please send Bitcoin donations to my address
3407 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3412 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
3413 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
3414 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
3415 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
3416 <description><p
>Every mobile phone announce its existence over radio to the nearby
3417 mobile cell towers. And this radio chatter is available for anyone
3418 with a radio receiver capable of receiving them. Details about the
3419 mobile phones with very good accuracy is of course collected by the
3420 phone companies, but this is not the topic of this blog post. The
3421 mobile phone radio chatter make it possible to figure out when a cell
3422 phone is nearby, as it include the SIM card ID (IMSI). By paying
3423 attention over time, one can see when a phone arrive and when it leave
3424 an area. I believe it would be nice to make this information more
3425 available to the general public, to make more people aware of how
3426 their phones are announcing their whereabouts to anyone that care to
3429 <p
>I am very happy to report that we managed to get something
3430 visualizing this information up and running for
3431 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
3432 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
3433 library. The solution is based on the
3434 <a href=
"https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
3435 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
3436 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
3437 Sone from the Computer Science department of the University of
3438 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
3439 IMSIs) as dots in a web browser graph, with lines to the dot
3440 representing mobile base station it is talking to. It was working in
3441 the lab yesterday, and was moved into place this morning.
</p
>
3443 <p
>We set up a fairly powerful desktop machine using Debian
3444 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
3445 connected and visualize the visible cell phone towers using an
3446 <a href=
"https://github.com/marlow925/hopglass
">English version of
3447 Hopglass
</a
>. A fairly powerfull machine is needed as the
3448 grgsm_livemon_headless processes from
3449 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
3450 the radio signal to data packages is quite CPU intensive.
</p
>
3452 <p
>The frequencies to listen to, are identified using a slightly
3453 patched scan-and-livemon (to set the --args values for each receiver),
3454 and the Hopglass data is generated using the
3455 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
3456 in my meshviewer-output branch
</a
>. For some reason we could not get
3457 more than four SDRs working. There is also a geographical map trying
3458 to show the location of the base stations, but I believe their
3459 coordinates are hardcoded to some random location in Germany, I
3460 believe. The code should be replaced with code to look up location in
3461 a text file, a sqlite database or one of the online databases
3463 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
3464 issue for the topic
</a
>.
3466 <p
>If this sound interesting, visit the stand at the festival!
</p
>
3471 <title>Easier recipe to observe the cell phones around you
</title>
3472 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
3473 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
3474 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
3475 <description><p
>A little more than a month ago I wrote
3476 <a href=
"https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
3477 to observe the SIM card ID (aka IMSI number) of mobile phones talking
3478 to nearby mobile phone base stations using Debian GNU/Linux and a
3479 cheap USB software defined radio
</a
>, and thus being able to pinpoint
3480 the location of people and equipment (like cars and trains) with an
3481 accuracy of a few kilometer. Since then we have worked to make the
3482 procedure even simpler, and it is now possible to do this without any
3483 manual frequency tuning and without building your own packages.
</p
>
3485 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
3486 package is now included in Debian testing and unstable, and the
3487 IMSI-catcher code no longer require root access to fetch and decode
3488 the GSM data collected using gr-gsm.
</p
>
3490 <p
>Here is an updated recipe, using packages built by Debian and a git
3491 clone of two python scripts:
</p
>
3495 <li
>Start with a Debian machine running the Buster version (aka
3496 testing).
</li
>
3498 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
3499 python-scapy
</tt
>' as root to install required packages.
</li
>
3501 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
3502 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
3504 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
3506 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
3507 scan-and-livemon
</tt
>' to locate the frequency of nearby base
3508 stations and start listening for GSM packages on one of them.
</li
>
3510 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
3511 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
3515 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
3516 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
3517 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
3518 work with RTL
8232 and other similar USB radio receivers you can get
3520 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
3521 from ebay
</a
>), so for now the solution is to scan using the RTL radio
3522 and only use HackRF for fetching GSM data.
</p
>
3524 <p
>As far as I can tell, a cell phone only show up on one of the
3525 frequencies at the time, so if you are going to track and count every
3526 cell phone around you, you need to listen to all the frequencies used.
3527 To listen to several frequencies, use the --numrecv argument to
3528 scan-and-livemon to use several receivers. Further, I am not sure if
3529 phones using
3G or
4G will show as talking GSM to base stations, so
3530 this approach might not see all phones around you. I typically see
3531 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
3533 <p
>I
've tried to run the scanner on a
3534 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
3535 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
3536 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
3537 stdout, I am told there it is caused by a buffer overflow between the
3538 radio and GNU Radio, caused by the program being unable to read the
3539 GSM data fast enough. If you see a stream of
'O
's from the terminal
3540 where you started scan-and-livemon, you need a give the process more
3541 CPU power. Perhaps someone are able to optimize the code to a point
3542 where it become possible to set up RPi3 based GSM sniffers? I tried
3543 using Raspbian instead of Debian, but there seem to be something wrong
3544 with GNU Radio on raspbian, causing glibc to abort().
</p
>
3549 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
3550 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
3551 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
3552 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
3553 <description><p
>On friday, I came across an interesting article in the Norwegian
3554 web based ICT news magazine digi.no on
3555 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
3556 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
3557 DVB-T software defined radios. The article refered to instructions
3558 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
3559 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
3561 <p
>The instructions said to use Ubuntu, install pip using apt (to
3562 bypass apt), use pip to install pybombs (to bypass both apt and pip),
3563 and the ask pybombs to fetch and build everything you need from
3564 scratch. I wanted to see if I could do the same on the most recent
3565 Debian packages, but this did not work because pybombs tried to build
3566 stuff that no longer build with the most recent openssl library or
3567 some other version skew problem. While trying to get this recipe
3568 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
3569 and the only piece of software dependency missing in Debian was the
3570 gr-gsm package. I also found out that the lead upstream developer of
3571 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
3572 Debian packages provided in an Ubuntu PPA repository. All I needed to
3573 do was to dget the Debian source package and built it.
</p
>
3575 <p
>The IMSI collector is a python script listening for packages on the
3576 loopback network device and printing to the terminal some specific GSM
3577 packages with IMSI numbers in them. The code is fairly short and easy
3578 to understand. The reason this work is because gr-gsm include a tool
3579 to read GSM data from a software defined radio like a DVB-T USB stick
3580 and other software defined radios, decode them and inject them into a
3581 network device on your Linux machine (using the loopback device by
3582 default). This proved to work just fine, and I
've been testing the
3583 collector for a few days now.
</p
>
3585 <p
>The updated and simpler recipe is thus to
</p
>
3589 <li
>start with a Debian machine running Stretch or newer,
</li
>
3591 <li
>build and install the gr-gsm package available from
3592 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
3594 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
3596 <li
>run grgsm_livemon and adjust the frequency until the terminal
3597 where it was started is filled with a stream of text (meaning you
3598 found a GSM station).
</li
>
3600 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
3604 <p
>To make it even easier in the future to get this sniffer up and
3605 running, I decided to package
3606 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
3607 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
3608 #
871055</a
>), and the package was uploaded into the NEW queue today.
3609 Luckily the gnuradio maintainer has promised to help me, as I do not
3610 know much about gnuradio stuff yet.
</p
>
3612 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
3613 commercial tools like
3614 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
3615 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
3616 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
3617 Stingray
</a
>, but I hope the existance of cheap alternatives can make
3618 more people realise how their whereabouts when carrying a cell phone
3619 is easily tracked. Seeing the data flow on the screen, realizing that
3620 I live close to a police station and knowing that the police is also
3621 wearing cell phones, I wonder how hard it would be for criminals to
3622 track the position of the police officers to discover when there are
3623 police near by, or for foreign military forces to track the location
3624 of the Norwegian military forces, or for anyone to track the location
3625 of government officials...
</p
>
3627 <p
>It is worth noting that the data reported by the IMSI-catcher
3628 script mentioned above is only a fraction of the data broadcasted on
3629 the GSM network. It will only collect one frequency at the time,
3630 while a typical phone will be using several frequencies, and not all
3631 phones will be using the frequencies tracked by the grgsm_livemod
3632 program. Also, there is a lot of radio chatter being ignored by the
3633 simple_IMSI-catcher script, which would be collected by extending the
3634 parser code. I wonder if gr-gsm can be set up to listen to more than
3635 one frequency?
</p
>
3640 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
3641 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
3642 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
3643 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
3644 <description><p align=
"center
"><img align=
"center
" src=
"https://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
3646 <p
>I finally received a copy of the Norwegian Bokmål edition of
3647 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
3648 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
3649 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
3650 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
3651 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
3652 price. The book is also available for download in electronic form as
3653 PDF, EPUB and Mobipocket, as can be
3654 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
3655 as a web page
</a
>.
</p
>
3657 <p
>This is the second book I publish (the first was the book
3658 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
3660 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
3661 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
3663 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
3664 Bokmål
</a
>), and I am very excited to finally wrap up this
3666 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
3667 for Debian-administratoren
</a
>" will be well received.
</p
>
3672 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
3673 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
3674 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
3675 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
3676 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
3677 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
3678 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
3679 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
3680 på om den fri oversetterløsningen
3681 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
3682 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
3684 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
3687 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
3688 rolle og muligheter til å håndtere internasjonale utfordringer, som
3689 for eksempel flykningekrisen.
</p
>
3691 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
3692 på temaet:
</p
>
3694 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
3695 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
3700 <p
>Dette oversetter Apertium slik:
</p
>
3703 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
3704 andre aktørar og høve til å handtera internasjonale utfordringar, som
3705 til dømes *flykningekrisen.
</p
>
3707 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
3711 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
3712 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
3717 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
3718 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
3719 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
3720 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
3721 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
3722 det er kanskje flisespikking. Det understreker vel bare at det alltid
3723 trengs korrekturlesning etter automatisk oversettelse.
</p
>
3728 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
3729 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
3730 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
3731 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
3732 <description><p
>Over the years, administrating thousand of NFS mounting linux
3733 computers at the time, I often needed a way to detect if the machine
3734 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
3735 file or directory affected by the hang, the process (and possibly the
3736 shell) will hang too. So you want to be able to detect this without
3737 risking the detection process getting stuck too. It has not been
3738 obvious how to do this. When the hang has lasted a while, it is
3739 possible to find messages like these in dmesg:
</p
>
3741 <p
><blockquote
>
3742 nfs: server nfsserver not responding, still trying
3743 <br
>nfs: server nfsserver OK
3744 </blockquote
></p
>
3746 <p
>It is hard to know if the hang is still going on, and it is hard to
3747 be sure looking in dmesg is going to work. If there are lots of other
3748 messages in dmesg the lines might have rotated out of site before they
3749 are noticed.
</p
>
3751 <p
>While reading through the nfs client implementation in linux kernel
3752 code, I came across some statistics that seem to give a way to detect
3753 it. The om_timeouts sunrpc value in the kernel will increase every
3754 time the above log entry is inserted into dmesg. And after digging a
3755 bit further, I discovered that this value show up in
3756 /proc/self/mountstats on Linux.
</p
>
3758 <p
>The mountstats content seem to be shared between files using the
3759 same file system context, so it is enough to check one of the
3760 mountstats files to get the state of the mount point for the machine.
3761 I assume this will not show lazy umounted NFS points, nor NFS mount
3762 points in a different process context (ie with a different filesystem
3763 view), but that does not worry me.
</p
>
3765 <p
>The content for a NFS mount point look similar to this:
</p
>
3767 <p
><blockquote
><pre
>
3769 device /dev/mapper/Debian-var mounted on /var with fstype ext3
3770 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
3771 opts: rw,vers=
3,rsize=
65536,wsize=
65536,namlen=
255,acregmin=
3,acregmax=
60,acdirmin=
30,acdirmax=
60,soft,nolock,proto=tcp,timeo=
600,retrans=
2,sec=sys,mountaddr=
129.240.3.145,mountvers=
3,mountport=
4048,mountproto=udp,local_lock=all
3773 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
3774 sec: flavor=
1,pseudoflavor=
1
3775 events:
61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
3776 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
3777 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
3778 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
3780 NULL:
0 0 0 0 0 0 0 0
3781 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
3782 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
3783 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
3784 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
3785 READLINK:
125 125 0 20472 18620 0 1112 1118
3786 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
3787 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
3788 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
3789 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
3790 SYMLINK:
903 903 0 233428 245488 6 5865 5917
3791 MKNOD:
80 80 0 20148 21760 0 299 304
3792 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
3793 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
3794 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
3795 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
3796 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
3797 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
3798 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
3799 FSINFO:
2 2 0 232 328 0 1 1
3800 PATHCONF:
1 1 0 116 140 0 0 0
3801 COMMIT:
0 0 0 0 0 0 0 0
3803 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
3805 </pre
></blockquote
></p
>
3807 <p
>The key number to look at is the third number in the per-op list.
3808 It is the number of NFS timeouts experiences per file system
3809 operation. Here
22 write timeouts and
5 access timeouts. If these
3810 numbers are increasing, I believe the machine is experiencing NFS
3811 hang. Unfortunately the timeout value do not start to increase right
3812 away. The NFS operations need to time out first, and this can take a
3813 while. The exact timeout value depend on the setup. For example the
3814 defaults for TCP and UDP mount points are quite different, and the
3815 timeout value is affected by the soft, hard, timeo and retrans NFS
3816 mount options.
</p
>
3818 <p
>The only way I have been able to get working on Debian and RedHat
3819 Enterprise Linux for getting the timeout count is to peek in /proc/.
3821 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
3822 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
3823 command can be used to get these timeout values. But this do not work
3824 on Linux, as far as I can tell. I
3825 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
3826 but have not seen any replies yet.
</p
>
3828 <p
>Is there a better way to figure out if a Linux NFS client is
3829 experiencing NFS hangs? Is there a way to detect which processes are
3830 affected? Is there a way to get the NFS mount going quickly once the
3831 network problem causing the NFS hang has been cleared? I would very
3832 much welcome some clues, as we regularly run into NFS hangs.
</p
>
3837 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
3838 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
3839 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</guid>
3840 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
3841 <description><p
>For almost a year now, we have been working on making a Norwegian
3842 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
3843 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
3844 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
3845 we are working on the proof reading to ensure consistent language and
3846 use of correct computer science terms. The plan is to make the book
3847 available on paper, as well as in electronic form. For that to
3848 happen, the proof reading must be completed and all the figures need
3849 to be translated. If you want to help out, get in touch.
</p
>
3851 <p
><a href=
"https://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
3853 fresh PDF edition
</a
> in A4 format (the final book will have smaller
3854 pages) of the book created every morning is available for
3855 proofreading. If you find any errors, please
3856 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
3857 Weblate and correct the error
</a
>. The
3858 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
3859 of the translation including figures
</a
> is a useful source for those
3860 provide Norwegian bokmål screen shots and figures.
</p
>
3865 <title>Unlimited randomness with the ChaosKey?
</title>
3866 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
3867 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
3868 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
3869 <description><p
>A few days ago I ordered a small batch of
3870 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
3871 USB dongle for generating entropy created by Bdale Garbee and Keith
3872 Packard. Yesterday it arrived, and I am very happy to report that it
3873 work great! According to its designers, to get it to work out of the
3874 box, you need the Linux kernel version
4.1 or later. I tested on a
3875 Debian Stretch machine (kernel version
4.9), and there it worked just
3876 fine, increasing the available entropy very quickly. I wrote a small
3877 test oneliner to test. It first print the current entropy level,
3878 drain /dev/random, and then print the entropy level for five seconds.
3879 Here is the situation without the ChaosKey inserted:
</p
>
3881 <blockquote
><pre
>
3882 % cat /proc/sys/kernel/random/entropy_avail; \
3883 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3884 for n in $(seq
1 5); do \
3885 cat /proc/sys/kernel/random/entropy_avail; \
3891 28 byte kopiert,
0,
000264565 s,
106 kB/s
3898 </pre
></blockquote
>
3900 <p
>The entropy level increases by
3-
4 every second. In such case any
3901 application requiring random bits (like a HTTPS enabled web server)
3902 will halt and wait for more entrpy. And here is the situation with
3903 the ChaosKey inserted:
</p
>
3905 <blockquote
><pre
>
3906 % cat /proc/sys/kernel/random/entropy_avail; \
3907 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3908 for n in $(seq
1 5); do \
3909 cat /proc/sys/kernel/random/entropy_avail; \
3915 104 byte kopiert,
0,
000487647 s,
213 kB/s
3922 </pre
></blockquote
>
3924 <p
>Quite the difference. :) I bought a few more than I need, in case
3925 someone want to buy one here in Norway. :)
</p
>
3927 <p
>Update: The dongle was presented at Debconf last year. You might
3928 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
3929 recording illuminating
</a
>. It explains exactly what the source of
3930 randomness is, if you are unable to spot it from the schema drawing
3931 available from the ChaosKey web site linked at the start of this blog
3937 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
3938 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
3939 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
3940 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
3941 <description><p
>Did you ever wonder where the web trafic really flow to reach the
3942 web servers, and who own the network equipment it is flowing through?
3943 It is possible to get a glimpse of this from using traceroute, but it
3944 is hard to find all the details. Many years ago, I wrote a system to
3945 map the Norwegian Internet (trying to figure out if our plans for a
3946 network game service would get low enough latency, and who we needed
3947 to talk to about setting up game servers close to the users. Back
3948 then I used traceroute output from many locations (I asked my friends
3949 to run a script and send me their traceroute output) to create the
3950 graph and the map. The output from traceroute typically look like
3953 <p
><pre
>
3954 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
3955 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
3956 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
3957 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
3958 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
3959 5 he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.627 ms he16-
1-
1.cr2.oslosda310.as2116.net (
195.0.244.48)
3.172 ms he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.857 ms
3960 6 ae1.ar8.oslosda310.as2116.net (
195.0.242.39)
0.662 ms
0.637 ms ae0.ar8.oslosda310.as2116.net (
195.0.242.23)
0.622 ms
3961 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
3965 </pre
></p
>
3967 <p
>This show the DNS names and IP addresses of (at least some of the)
3968 network equipment involved in getting the data traffic from me to the
3969 www.stortinget.no server, and how long it took in milliseconds for a
3970 package to reach the equipment and return to me. Three packages are
3971 sent, and some times the packages do not follow the same path. This
3972 is shown for hop
5, where three different IP addresses replied to the
3973 traceroute request.
</p
>
3975 <p
>There are many ways to measure trace routes. Other good traceroute
3976 implementations I use are traceroute (using ICMP packages) mtr (can do
3977 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
3978 traceroute and a lot of other capabilities). All of them are easily
3979 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
3981 <p
>This time around, I wanted to know the geographic location of
3982 different route points, to visualize how visiting a web page spread
3983 information about the visit to a lot of servers around the globe. The
3984 background is that a web site today often will ask the browser to get
3985 from many servers the parts (for example HTML, JSON, fonts,
3986 JavaScript, CSS, video) required to display the content. This will
3987 leak information about the visit to those controlling these servers
3988 and anyone able to peek at the data traffic passing by (like your ISP,
3989 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
3991 <p
>Lets pick an example, the Norwegian parliament web site
3992 www.stortinget.no. It is read daily by all members of parliament and
3993 their staff, as well as political journalists, activits and many other
3994 citizens of Norway. A visit to the www.stortinget.no web site will
3995 ask your browser to contact
8 other servers: ajax.googleapis.com,
3996 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3997 stats.g.doubleclick.net, www.google-analytics.com,
3998 www.googletagmanager.com and www.netigate.se. I extracted this by
3999 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
4000 Stortinget web page and tell me all the URLs PhantomJS downloaded to
4001 render the page (in HAR format using
4002 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
4003 netsniff example
</a
>. I am very grateful to Gorm for showing me how
4004 to do this). My goal is to visualize network traces to all IP
4005 addresses behind these DNS names, do show where visitors personal
4006 information is spread when visiting the page.
</p
>
4008 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
4009 src=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geoip-small.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using GeoIP
"/
></a
></p
>
4011 <p
>When I had a look around for options, I could not find any good
4012 free software tools to do this, and decided I needed my own traceroute
4013 wrapper outputting KML based on locations looked up using GeoIP. KML
4014 is easy to work with and easy to generate, and understood by several
4015 of the GIS tools I have available. I got good help from by NUUG
4016 colleague Anders Einar with this, and the result can be seen in
4017 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
4018 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
4019 free GeoIP databases I could find (and the for-pay databases my
4020 friends had access to) is not up to the task. The IP addresses of
4021 central Internet infrastructure would typically be placed near the
4022 controlling companies main office, and not where the router is really
4023 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
4024 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
4026 <p align=
"center
"><a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
4027 src=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy-small.png
" alt=
"scapy traceroute graph for URLs used by www.stortinget.no
"/
></a
></p
>
4029 <p
>I also had a look at the visual traceroute graph created by
4030 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
4031 showing IP network ownership (aka AS owner) for the IP address in
4033 <a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
4034 graph display a lot of useful information about the traceroute in SVG
4035 format
</a
>, and give a good indication on who control the network
4036 equipment involved, but it do not include geolocation. This graph
4037 make it possible to see the information is made available at least for
4038 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
4039 3 Communications and NetDNA.
</p
>
4041 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
4042 src=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-small.png
" alt=
"example geotraceroute view for www.stortinget.no
"/
></a
></p
>
4044 <p
>In the process, I came across the
4045 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
4046 Salim Gasmi. Its methology of combining guesses based on DNS names,
4047 various location databases and finally use latecy times to rule out
4048 candidate locations seemed to do a very good job of guessing correct
4049 geolocation. But it could only do one trace at the time, did not have
4050 a sensor in Norway and did not make the geolocations easily available
4051 for postprocessing. So I contacted the developer and asked if he
4052 would be willing to share the code (he refused until he had time to
4053 clean it up), but he was interested in providing the geolocations in a
4054 machine readable format, and willing to set up a sensor in Norway. So
4055 since yesterday, it is possible to run traces from Norway in this
4056 service thanks to a sensor node set up by
4057 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
4058 trace in KML format for further processing.
</p
>
4060 <p align=
"center
"><a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
4061 src=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using geotraceroute
"/
></a
></p
>
4063 <p
>Here we can see a lot of trafic passes Sweden on its way to
4064 Denmark, Germany, Holland and Ireland. Plenty of places where the
4065 Snowden confirmations verified the traffic is read by various actors
4066 without your best interest as their top priority.
</p
>
4068 <p
>Combining KML files is trivial using a text editor, so I could loop
4069 over all the hosts behind the urls imported by www.stortinget.no and
4070 ask for the KML file from GeoTraceroute, and create a combined KML
4071 file with all the traces (unfortunately only one of the IP addresses
4072 behind the DNS name is traced this time. To get them all, one would
4073 have to request traces using IP number instead of DNS names from
4074 GeoTraceroute). That might be the next step in this project.
</p
>
4076 <p
>Armed with these tools, I find it a lot easier to figure out where
4077 the IP traffic moves and who control the boxes involved in moving it.
4078 And every time the link crosses for example the Swedish border, we can
4079 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
4080 Britain and NSA in USA and cables around the globe. (Hm, what should
4081 we tell them? :) Keep that in mind if you ever send anything
4082 unencrypted over the Internet.
</p
>
4084 <p
>PS: KML files are drawn using
4085 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
4086 Rublev
<a/
>, as it was less cluttered than the local Linux application
4087 Marble. There are heaps of other options too.
</p
>
4089 <p
>As usual, if you use Bitcoin and want to show your support of my
4090 activities, please send Bitcoin donations to my address
4091 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4096 <title>Appstream just learned how to map hardware to packages too!
</title>
4097 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
4098 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
4099 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
4100 <description><p
>I received a very nice Christmas present today. As my regular
4101 readers probably know, I have been working on the
4102 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
4103 system
</a
> for many years. The goal of the Isenkram system is to make
4104 it easier for users to figure out what to install to get a given piece
4105 of hardware to work in Debian, and a key part of this system is a way
4106 to map hardware to packages. Isenkram have its own mapping database,
4107 and also uses data provided by each package using the AppStream
4108 metadata format. And today,
4109 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
4110 Debian learned to look up hardware the same way Isenkram is doing it,
4111 ie using fnmatch():
</p
>
4113 <p
><pre
>
4114 % appstreamcli what-provides modalias \
4115 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
4116 Identifier: pymissile [generic]
4118 Summary: Control original Striker USB Missile Launcher
4120 % appstreamcli what-provides modalias usb:v0694p0002d0000
4121 Identifier: libnxt [generic]
4123 Summary: utility library for talking to the LEGO Mindstorms NXT brick
4126 Identifier: t2n [generic]
4128 Summary: Simple command-line tool for Lego NXT
4131 Identifier: python-nxt [generic]
4133 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
4136 Identifier: nbc [generic]
4138 Summary: C compiler for LEGO Mindstorms NXT bricks
4141 </pre
></p
>
4143 <p
>A similar query can be done using the combined AppStream and
4144 Isenkram databases using the isenkram-lookup tool:
</p
>
4146 <p
><pre
>
4147 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
4149 % isenkram-lookup usb:v0694p0002d0000
4155 </pre
></p
>
4157 <p
>You can find modalias values relevant for your machine using
4158 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
4160 <p
>If you want to make this system a success and help Debian users
4161 make the most of the hardware they have, please help
4162 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
4163 metadata for your package following the guidelines
</a
> documented in
4164 the wiki. So far only
11 packages provide such information, among the
4165 several hundred hardware specific packages in Debian. The Isenkram
4166 database on the other hand contain
101 packages, mostly related to USB
4167 dongles. Most of the packages with hardware mapping in AppStream are
4168 LEGO Mindstorms related, because I have, as part of my involvement in
4169 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
4170 team
</a
> given priority to making sure LEGO users get proposed the
4171 complete set of packages in Debian for that particular hardware. The
4172 team also got a nice Christmas present today. The
4173 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
4174 package
</a
> made it into Debian. With this package in place, it is
4175 now possible to use the LEGO Mindstorms NXT unit with only free
4176 software, as the nxt-firmware package contain the source and firmware
4177 binaries for the NXT brick.
</p
>
4179 <p
>As usual, if you use Bitcoin and want to show your support of my
4180 activities, please send Bitcoin donations to my address
4181 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4186 <title>Isenkram updated with a lot more hardware-package mappings
</title>
4187 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
4188 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
4189 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
4190 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
4191 system
</a
> I wrote two years ago to make it easier in Debian to find
4192 and install packages to get your hardware dongles to work, is still
4193 going strong. It is a system to look up the hardware present on or
4194 connected to the current system, and map the hardware to Debian
4195 packages. It can either be done using the tools in isenkram-cli or
4196 using the user space daemon in the isenkram package. The latter will
4197 notify you, when inserting new hardware, about what packages to
4198 install to get the dongle working. It will even provide a button to
4199 click on to ask packagekit to install the packages.
</p
>
4201 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
4203 <p
><pre
>
4220 </pre
></p
>
4222 <p
>It can also list the firware package providing firmware requested
4223 by the load kernel modules, which in my case is an empty list because
4224 I have all the firmware my machine need:
4226 <p
><pre
>
4227 % /usr/sbin/isenkram-autoinstall-firmware -l
4228 info: did not find any firmware files requested by loaded kernel modules. exiting
4230 </pre
></p
>
4232 <p
>The last few days I had a look at several of the around
250
4233 packages in Debian with udev rules. These seem like good candidates
4234 to install when a given hardware dongle is inserted, and I found
4235 several that should be proposed by isenkram. I have not had time to
4236 check all of them, but am happy to report that now there are
97
4237 packages packages mapped to hardware by Isenkram.
11 of these
4238 packages provide hardware mapping using AppStream, while the rest are
4239 listed in the modaliases file provided in isenkram.
</p
>
4241 <p
>These are the packages with hardware mappings at the moment. The
4242 <strong
>marked packages
</strong
> are also announcing their hardware
4243 support using AppStream, for everyone to use:
</p
>
4245 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
4246 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
4247 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
4248 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
4249 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
4250 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
4251 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
4252 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
4253 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
4254 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
4255 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
4256 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
4257 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
4258 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
4259 pcscd, pidgin-blinklight, printer-driver-splix,
4260 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
4261 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
4262 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
4263 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
4264 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
4265 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
4266 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
4267 xserver-xorg-video-vmware, yubikey-personalization and
4268 zd1211-firmware
</p
>
4270 <p
>If you know of other packages, please let me know with a wishlist
4271 bug report against the isenkram-cli package, and ask the package
4273 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
4274 metadata according to the guidelines
</a
> to provide the information
4275 for everyone. In time, I hope to get rid of the isenkram specific
4276 hardware mapping and depend exclusively on AppStream.
</p
>
4278 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
4279 much hardware, and suggest that the package with with any ethernet
4280 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
4281 the details. I hope the maintainer find time to address it soon. In
4282 the mean time I provide an override in isenkram.
</p
>
4287 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
4288 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
4289 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
4290 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
4291 <description><p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
4293 <p
>In my early years, I played
4294 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
4295 Elite
</a
> on my PC. I spent many months trading and fighting in
4296 space, and reached the
'elite
' fighting status before I moved on. The
4297 original Elite game was available on Commodore
64 and the IBM PC
4298 edition I played had a
64 KB executable. I am still impressed today
4299 that the authors managed to squeeze both a
3D engine and details about
4300 more than
2000 planet systems across
7 galaxies into a binary so
4303 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
4304 software game Oolite inspired by Elite
</a
> for a while, but did not
4305 really have time to test it properly until a few days ago. It was
4306 great to discover that my old knowledge about trading routes were
4307 still valid. But my fighting and flying abilities were gone, so I had
4308 to retrain to be able to dock on a space station. And I am still not
4309 able to make much resistance when I am attacked by pirates, so I
4310 bougth and mounted the most powerful laser in the rear to be able to
4311 put up at least some resistance while fleeing for my life. :)
</p
>
4313 <p
>When playing Elite in the late eighties, I had to discover
4314 everything on my own, and I had long lists of prices seen on different
4315 planets to be able to decide where to trade what. This time I had the
4317 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
4318 where information about each planet is easily available with common
4319 price ranges and suggested trading routes. This improved my ability
4320 to earn money and I have been able to earn enough to buy a lot of
4321 useful equipent in a few days. I believe I originally played for
4322 months before I could get a docking computer, while now I could get it
4323 after less then a week.
</p
>
4325 <p
>If you like science fiction and dreamed of a life as a vagabond in
4326 space, you should try out Oolite. It is available for Linux, MacOSX
4327 and Windows, and is included in Debian and derivatives since
2011.
</p
>
4329 <p
>As usual, if you use Bitcoin and want to show your support of my
4330 activities, please send Bitcoin donations to my address
4331 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4336 <title>Quicker Debian installations using eatmydata
</title>
4337 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
4338 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
4339 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
4340 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
4341 installation system, observing how using
4342 <a href=
"https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
4343 could speed up the installation
</a
> quite a bit. My testing measured
4344 speedup around
20-
40 percent for Debian Edu, where we install around
4345 1000 packages from within the installer. The eatmydata package
4346 provide a way to disable/delay file system flushing. This is a bit
4347 risky in the general case, as files that should be stored on disk will
4348 stay only in memory a bit longer than expected, causing problems if a
4349 machine crashes at an inconvenient time. But for an installation, if
4350 the machine crashes during installation the process is normally
4351 restarted, and avoiding disk operations as much as possible to speed
4352 up the process make perfect sense.
4354 <p
>I added code in the Debian Edu specific installation code to enable
4355 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
4356 but did not have time to push it any further. But a few months ago I
4357 picked it up again and worked with the libeatmydata package maintainer
4358 Mattia Rizzolo to make it easier for everyone to get this installation
4359 speedup in Debian. Thanks to our cooperation There is now an
4360 eatmydata-udeb package in Debian testing and unstable, and simply
4361 enabling/installing it in debian-installer (d-i) is enough to get the
4362 quicker installations. It can be enabled using preseeding. The
4363 following untested kernel argument should do the trick:
</p
>
4365 <blockquote
><pre
>
4366 preseed/early_command=
"anna-install eatmydata-udeb
"
4367 </pre
></blockquote
>
4369 <p
>This should ask d-i to install the package inside the d-i
4370 environment early in the installation sequence. Having it installed
4371 in d-i in turn will make sure the relevant scripts are called just
4372 after debootstrap filled /target/ with the freshly installed Debian
4373 system to configure apt to run dpkg with eatmydata. This is enough to
4374 speed up the installation process. There is a proposal to
4375 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
4376 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
4377 tested its impact.
</p
>
4383 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
4384 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
4385 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
4386 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
4387 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
4388 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
4389 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
4390 elever over det ganske land skal levere inn hvert år. Det mange ikke
4391 vet er at selv om de kommersielle alternativene
4392 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
4393 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
4394 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
4395 utmerket fri programvarealternativ som kan. Oversetterverktøyet
4396 Apertium har støtte for en rekke språkkombinasjoner, og takket være
4397 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
4398 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
4399 nynorsk, og få den automatoversatt til det andre skriftspråket.
4400 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
4401 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
4402 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
4403 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
4404 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
4405 teksten din i webskjemaet der.
4407 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
4408 teknologien kan du enten installere pakken
4409 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
4410 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
4411 api.apertium.org. Se
4412 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
4413 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
4414 denne teksten som ble skrevet på bokmål over maskinoversatt til
4419 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
4420 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
4421 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
4422 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
4423 veit er at sjølv om dei kommersielle alternativa
4424 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
4425 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
4426 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
4427 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
4428 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
4429 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
4430 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
4431 nynorsk, og få den *automatoversatt til det andre skriftspråket.
4432 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
4433 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
4434 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
4435 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
4436 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
4437 teksta di i *webskjemaet der.
4439 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
4440 teknologien kan du anten installera pakken
4441 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
4442 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
4443 *api.*apertium.org. Sjå
4444 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
4445 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
4446 for denne teksta som vart skreva på bokmål over *maskinoversatt til
4452 <title>Coz profiler for multi-threaded software is now in Debian
</title>
4453 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
4454 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
4455 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
4456 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
4457 profiler able to run benchmarking experiments on the instrumented
4458 multi-threaded program, finally
4459 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
4460 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
4462 <a href=
"https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
4463 blogged about the coz tool
</a
> in August working with upstream to make
4464 it suitable for Debian. There are still issues with clang
4465 compatibility, inline assembly only working x86 and minimized
4466 JavaScript libraries.
</p
>
4468 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
4470 <p
><blockquote
>
4471 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
4472 </blockquote
></p
>
4474 <p
>This will produce a profile.coz file in the current working
4475 directory with the profiling information. This is then given to a
4476 JavaScript application provided in the package and available from
4477 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
4478 To start the local copy, invoke it in a browser like this:
</p
>
4480 <p
><blockquote
>
4481 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
4482 </blockquote
></p
>
4484 <p
>See the project home page and the
4485 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
4486 ;login: article on Coz
</a
> for more information on how it is
4492 <title>My own self balancing Lego Segway
</title>
4493 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
4494 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
4495 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
4496 <description><p
>A while back I received a Gyro sensor for the NXT
4497 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
4498 present. It had been on my wishlist for a while, because I wanted to
4499 build a Segway like balancing lego robot. I had already built
4500 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
4501 robot
</a
> with the kids, using the light/color sensor included in the
4502 NXT kit as the balance sensor, but it was not working very well. It
4503 could balance for a while, but was very sensitive to the light
4504 condition in the room and the reflective properties of the surface and
4505 would fall over after a short while. I wanted something more robust,
4507 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
4508 gyro sensor from HiTechnic
</a
> I believed would solve it on my
4509 wishlist for some years before it suddenly showed up as a gift from my
4510 loved ones. :)
</p
>
4512 <p
>Unfortunately I have not had time to sit down and play with it
4513 since then. But that changed some days ago, when I was searching for
4514 lego segway information and came across a recipe from HiTechnic for
4516 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
4517 HTWay
</a
>, a segway like balancing robot. Build instructions and
4518 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
4519 code
</a
> was included, so it was just a question of putting it all
4520 together. And thanks to the great work of many Debian developers, the
4521 compiler needed to build the source for the NXT is already included in
4522 Debian, so I was read to go in less than an hour. The resulting robot
4523 do not look very impressive in its simplicity:
</p
>
4525 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
4527 <p
>Because I lack the infrared sensor used to control the robot in the
4528 design from HiTechnic, I had to comment out the last task
4529 (taskControl). I simply placed /* and */ around it get the program
4530 working without that sensor present. Now it balances just fine until
4531 the battery status run low:
</p
>
4533 <p align=
"center
"><video width=
"70%
" controls=
"true
">
4534 <source src=
"https://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
4535 </video
></p
>
4537 <p
>Now we would like to teach it how to follow a line and take remote
4538 control instructions using the included Bluetooth receiver in the NXT.
</p
>
4540 <p
>If you, like me, love LEGO and want to make sure we find the tools
4541 they need to work with LEGO in Debian and all our derivative
4542 distributions like Ubuntu, check out
4543 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
4544 project page
</a
> and join the Debian LEGO team. Personally I own a
4545 RCX and NXT controller (no EV3), and would like to make sure the
4546 Debian tools needed to program the systems I own work as they
4552 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
4553 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
4554 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
4555 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
4556 <description><p
>In July
4557 <a href=
"https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
4558 wrote how to get the Signal Chrome/Chromium app working
</a
> without
4559 the ability to receive SMS messages (aka without a cell phone). It is
4560 time to share some experiences and provide an updated setup.
</p
>
4562 <p
>The Signal app have worked fine for several months now, and I use
4563 it regularly to chat with my loved ones. I had a major snag at the
4564 end of my summer vacation, when the the app completely forgot my
4565 setup, identity and keys. The reason behind this major mess was
4566 running out of disk space. To avoid that ever happening again I have
4567 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
4568 roll back to an earlier version if the files are wiped by mistake. I
4569 had to use it once after introducing the git backup. When rolling
4570 back to an earlier version, one need to use the
'reset session
' option
4571 in Signal to get going, and notify the people you talk with about the
4572 problem. I assume there is some sequence number tracking in the
4573 protocol to detect rollback attacks. The git repository is rather big
4574 (
674 MiB so far), but I have not tried to figure out if some of the
4575 content can be added to a .gitignore file due to lack of spare
4578 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
4579 make it impossible to send messages using Signal. I could still
4580 receive them, but had to patch the code with a new timestamp to send.
4581 I believe the timeout is added by the developers to force people to
4582 upgrade to the latest version of the app, even when there is no
4583 protocol changes, to reduce the version skew among the user base and
4584 thus try to keep the number of support requests down.
</p
>
4586 <p
>Since my original recipe, the Signal source code changed slightly,
4587 making the old patch fail to apply cleanly. Below is an updated
4588 patch, including the shell wrapper I use to start Signal. The
4589 original version required a new user to locate the JavaScript console
4590 and call a function from there. I got help from a friend with more
4591 JavaScript knowledge than me to modify the code to provide a GUI
4592 button instead. This mean that to get started you just need to run
4593 the wrapper and click the
'Register without mobile phone
' to get going
4594 now. I
've also modified the timeout code to always set it to
90 days
4595 in the future, to avoid having to patch the code regularly.
</p
>
4597 <p
>So, the updated recipe for Debian Jessie:
</p
>
4601 <li
>First, install required packages to get the source code and the
4602 browser you need. Signal only work with Chrome/Chromium, as far as I
4603 know, so you need to install it.
4606 apt install git tor chromium
4607 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4608 </pre
></li
>
4610 <li
>Modify the source code using command listed in the the patch
4611 block below.
</li
>
4613 <li
>Start Signal using the run-signal-app wrapper (for example using
4614 <tt
>`pwd`/run-signal-app
</tt
>).
4616 <li
>Click on the
'Register without mobile phone
', will in a phone
4617 number you can receive calls to the next minute, receive the
4618 verification code and enter it into the form field and press
4619 'Register
'. Note, the phone number you use will be user Signal
4620 username, ie the way others can find you on Signal.
</li
>
4622 <li
>You can now use Signal to contact others. Note, new contacts do
4623 not show up in the contact list until you restart Signal, and there is
4624 no way to assign names to Contacts. There is also no way to create or
4625 update chat groups. I suspect this is because the web app do not have
4626 a associated contact database.
</li
>
4630 <p
>I am still a bit uneasy about using Signal, because of the way its
4631 main author moxie0 reject federation and accept dependencies to major
4632 corporations like Google (part of the code is fetched from Google) and
4633 Amazon (the central coordination point is owned by Amazon). See for
4635 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
4636 LibreSignal issue tracker
</a
> for a thread documenting the authors
4637 view on these issues. But the network effect is strong in this case,
4638 and several of the people I want to communicate with already use
4639 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
4640 once it
<a href=
"https://bugs.debian.org/
830265">work on my
4641 laptop
</a
>? It already work on Windows and Android, and is included
4642 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
4643 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
4644 working on Debian Stable.
</p
>
4646 <p
>Anyway, this is the patch I apply to the Signal code to get it
4647 working. It switch to the production servers, disable to timeout,
4648 make registration easier and add the shell wrapper:
</p
>
4651 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
4652 diff --git a/js/background.js b/js/background.js
4653 index
24b4c1d.
.579345f
100644
4654 --- a/js/background.js
4655 +++ b/js/background.js
4660 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
4661 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
4662 var SERVER_PORTS = [
80,
4433,
8443];
4663 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
4664 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
4665 var messageReceiver;
4666 window.getSocketStatus = function() {
4667 if (messageReceiver) {
4668 diff --git a/js/expire.js b/js/expire.js
4669 index
639aeae..beb91c3
100644
4674 'use strict
';
4675 - var BUILD_EXPIRATION =
0;
4676 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
4678 window.extension = window.extension || {};
4680 diff --git a/js/views/install_view.js b/js/views/install_view.js
4681 index
7816f4f.
.1d6233b
100644
4682 --- a/js/views/install_view.js
4683 +++ b/js/views/install_view.js
4686 'click .step1
': this.selectStep.bind(this,
1),
4687 'click .step2
': this.selectStep.bind(this,
2),
4688 -
'click .step3
': this.selectStep.bind(this,
3)
4689 +
'click .step3
': this.selectStep.bind(this,
3),
4690 +
'click .callreg
': function() { extension.install(
'standalone
') },
4693 clearQR: function() {
4694 diff --git a/options.html b/options.html
4695 index dc0f28e.
.8d709f6
100644
4699 &lt;div class=
'nav
'>
4700 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
4701 &lt;p
>{{ installTagline }}
&lt;/p
>
4702 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
4703 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
4704 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
4707 &lt;span class=
'dot step1 selected
'>&lt;/span
>
4708 &lt;span class=
'dot step2
'>&lt;/span
>
4709 &lt;span class=
'dot step3
'>&lt;/span
>
4710 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
4711 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
4717 +userdata=
"`pwd`/userdata
"
4718 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
4719 + (cd $userdata
&& git init)
4721 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
4723 + --proxy-server=
"socks://localhost:
9050" \
4724 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
4726 chmod a+rx run-signal-app
4729 <p
>As usual, if you use Bitcoin and want to show your support of my
4730 activities, please send Bitcoin donations to my address
4731 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4736 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
4737 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
4738 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
4739 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
4740 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
4741 system
</a
> provide a practical and easy way to figure out which
4742 packages support the hardware in a given machine. The command line
4743 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
4744 convenient way to list and install packages relevant for the current
4745 hardware during system installation, both user space packages and
4746 firmware packages. The GUI background daemon on the other hand provide
4747 a pop-up proposing to install packages when a new dongle is inserted
4748 while using the computer. For example, if you plug in a smart card
4749 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
4750 that package isn
't already installed, and if you plug in a USB video
4751 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
4752 cheese is currently missing. This already work just fine.
</p
>
4754 <p
>But Isenkram depend on a database mapping from hardware IDs to
4755 package names. When I started no such database existed in Debian, so
4756 I made my own data set and included it with the isenkram package and
4757 made isenkram fetch the latest version of this database from git using
4758 http. This way the isenkram users would get updated package proposals
4759 as soon as I learned more about hardware related packages.
</p
>
4761 <p
>The hardware is identified using modalias strings. The modalias
4762 design is from the Linux kernel where most hardware descriptors are
4763 made available as a strings that can be matched using filename style
4764 globbing. It handle USB, PCI, DMI and a lot of other hardware related
4765 identifiers.
</p
>
4767 <p
>The downside to the Isenkram specific database is that there is no
4768 information about relevant distribution / Debian version, making
4769 isenkram propose obsolete packages too. But along came AppStream, a
4770 cross distribution mechanism to store and collect metadata about
4771 software packages. When I heard about the proposal, I contacted the
4772 people involved and suggested to add a hardware matching rule using
4773 modalias strings in the specification, to be able to use AppStream for
4774 mapping hardware to packages. This idea was accepted and AppStream is
4775 now a great way for a package to announce the hardware it support in a
4776 distribution neutral way. I wrote
4777 <a href=
"https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
4778 recipe on how to add such meta-information
</a
> in a blog post last
4779 December. If you have a hardware related package in Debian, please
4780 announce the relevant hardware IDs using AppStream.
</p
>
4782 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
4783 RCX or NXT unit, announce this support using AppStream. The effect is
4784 that when you insert such LEGO robot controller into your Debian
4785 machine, Isenkram will propose to install the packages needed to get
4786 it working. The intention is that this should allow the local user to
4787 start programming his robot controller right away without having to
4788 guess what packages to use or which permissions to fix.
</p
>
4790 <p
>But when I sat down with my son the other day to program our NXT
4791 unit using his Debian Stretch computer, I discovered something
4792 annoying. The local console user (ie my son) did not get access to
4793 the USB device for programming the unit. This used to work, but no
4794 longer in Jessie and Stretch. After some investigation and asking
4795 around on #debian-devel, I discovered that this was because udev had
4796 changed the mechanism used to grant access to local devices. The
4797 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
4798 no longer applied, because LDAP users no longer was added to the
4799 plugdev group during login. Michael Biebl told me that this method
4800 was obsolete and the new method used ACLs instead. This was good
4801 news, as the plugdev mechanism is a mess when using a remote user
4802 directory like LDAP. Using ACLs would make sure a user lost device
4803 access when she logged out, even if the user left behind a background
4804 process which would retain the plugdev membership with the ConsoleKit
4805 setup. Armed with this knowledge I moved on to fix the access problem
4806 for the LEGO Mindstorms related packages.
</p
>
4808 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
4809 applied directly for a device, or is applied in
4810 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
4811 LEGO Mindstorms udev rules did not have a class, I decided to add the
4812 tag directly in the udev rules files included in the packages. Here
4813 is one example. For the nqc C compiler for the RCX, the
4814 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
4816 <p
><pre
>
4817 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
4818 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
4819 </pre
></p
>
4821 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
4822 packages using plugdev in their /lib/udev/rules.d/ files should be
4823 changed to use this tag (either directly or indirectly via
4824 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
4825 to detect this?
</p
>
4827 <p
>I
've been unable to find good documentation on the uaccess feature.
4828 It is unclear to me if the uaccess tag is an internal implementation
4829 detail like the udev-acl tag used by
4830 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
4831 indirect method is the preferred way. Michael
4832 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
4833 documentation from the systemd project
</a
> and I hope it will make
4834 this clearer. For now I use the generic classes when they exist and
4835 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
4836 directly if no such class exist.
</p
>
4838 <p
>To learn more about the isenkram system, please check out
4839 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4840 blog posts tagged isenkram
</a
>.
</p
>
4842 <p
>To help out making life for LEGO constructors in Debian easier,
4843 please join us on our IRC channel
4844 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
4845 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
4846 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
4847 list is not yet created, but we are working on it. :)
</p
>
4849 <p
>As usual, if you use Bitcoin and want to show your support of my
4850 activities, please send Bitcoin donations to my address
4851 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4856 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
4857 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
4858 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</guid>
4859 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
4860 <description><p
>In April we
4861 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
4862 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
4863 how to set up and administrate a Debian system. Today I am happy to
4864 report that the first draft is now publicly available. You can find
4865 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
4866 Administrator
's Handbook page
</a
> (under Other languages). The first
4867 eight chapters have a first draft translation, and we are working on
4868 proofreading the content. If you want to help out, please start
4870 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4871 hosted weblate project page
</a
>, and get in touch using
4872 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4873 translators mailing list
</a
>. Please also check out
4874 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4875 contributors
</a
>. A good way to contribute is to proofread the text
4876 and update weblate if you find errors.
</p
>
4878 <p
>Our goal is still to make the Norwegian book available on paper as well as
4879 electronic form.
</p
>
4884 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
4885 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
4886 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
4887 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
4888 <description><p
>This summer, I read a great article
4889 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
4890 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
4891 how to profile multi-threaded programs. It presented a system for
4892 profiling software by running experiences in the running program,
4893 testing how run time performance is affected by
"speeding up
" parts of
4894 the code to various degrees compared to a normal run. It does this by
4895 slowing down parallel threads while the
"faster up
" code is running
4896 and measure how this affect processing time. The processing time is
4897 measured using probes inserted into the code, either using progress
4898 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
4899 can also measure unmodified code by measuring complete the program
4900 runtime and running the program several times instead.
</p
>
4902 <p
>The project and presentation was so inspiring that I would like to
4903 get the system into Debian. I
4904 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
4905 a WNPP request for it
</a
> and contacted upstream to try to make the
4906 system ready for Debian by sending patches. The build process need to
4907 be changed a bit to avoid running
'git clone
' to get dependencies, and
4908 to include the JavaScript web page used to visualize the collected
4909 profiling information included in the source package.
4910 But I expect that should work out fairly soon.
</p
>
4912 <p
>The way the system work is fairly simple. To run an coz experiment
4913 on a binary with debug symbols available, start the program like this:
4915 <p
><blockquote
><pre
>
4916 coz run --- program-to-run
4917 </pre
></blockquote
></p
>
4919 <p
>This will create a text file profile.coz with the instrumentation
4920 information. To show what part of the code affect the performance
4921 most, use a web browser and either point it to
4922 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
4923 or use the copy from git (in the gh-pages branch). Check out this web
4924 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
4925 profiling more useful you include
&lt;coz.h
&gt; and insert the
4926 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
4927 code, rebuild and run the profiler. This allow coz to do more
4928 targeted experiments.
</p
>
4930 <p
>A video published by ACM
4931 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
4932 Coz profiler
</a
> is available from Youtube. There is also a paper
4933 from the
25th Symposium on Operating Systems Principles available
4935 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
4936 finding code that counts with causal profiling
</a
>.
</p
>
4938 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
4939 for Coz is available from github. It will only build with clang
4941 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
4942 feature missing in GCC
</a
>, but I
've submitted
4943 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
4944 it
</a
> and hope it will be included in the upstream source soon.
</p
>
4946 <p
>Please get in touch if you, like me, would like to see this piece
4947 of software in Debian. I would very much like some help with the
4948 packaging effort, as I lack the in depth knowledge on how to package
4949 C++ libraries.
</p
>
4954 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
4955 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
4956 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
4957 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
4958 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
4959 to be a slight challenge. Here is the recipe if I ever need to do it
4960 again. It all started by me wanting to try the recipe to set up
4961 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
4962 hardened Android installation
</a
> from the Tor project blog on a
4963 device I had access to. It is a old mobile phone with a broken
4964 microphone The initial idea had been to just
4965 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
4966 CyanogenMod on it
</a
>, but did not quite find time to start on it
4967 until a few days ago.
</p
>
4969 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
4970 loader (press volume down and power at the same time), (
2) select
4971 'fastboot
' before (
3) connecting the device via USB to a Linux
4972 machine, (
4) request the device identifier token by running
'fastboot
4973 oem get_identifier_token
', (
5) request the device unlocking key using
4974 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
4975 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
4977 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
4978 or newer, and the device I was working on had
2.00.0027. This
4979 apparently can be easily fixed by downloading a Windows program and
4980 running it on your Windows machine, if you accept the terms Microsoft
4981 require you to accept to use Windows - which I do not. So I had to
4982 come up with a different approach. I got a lot of help from AndyCap
4983 on #nuug, and would not have been able to get this working without
4986 <p
>First I needed to extract the hboot firmware from
4987 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
4988 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
4989 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
4990 project named unruu
</a
> using libunshield. The unshield tool did not
4991 recognise the file format, but unruu worked and extracted rom.zip,
4992 containing the new hboot firmware and a text file describing which
4993 devices it would work for.
</p
>
4995 <p
>Next, I needed to get the new firmware into the device. For this I
4996 followed some instructions
4997 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
4998 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
4999 machine with Debian testing:
</p
>
5001 <p
><pre
>
5002 adb reboot-bootloader
5003 fastboot oem rebootRUU
5004 fastboot flash zip rom.zip
5005 fastboot flash zip rom.zip
5007 </pre
></p
>
5009 <p
>The flash command apparently need to be done twice to take effect,
5010 as the first is just preparations and the second one do the flashing.
5011 The adb command is just to get to the boot loader menu, so turning the
5012 device on while holding volume down and the power button should work
5015 <p
>With the new hboot version in place I could start following the
5016 instructions on the HTC developer web site. I got the device token
5017 like this:
</p
>
5019 <p
><pre
>
5020 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
5023 <p
>And once I got the unlock code via email, I could use it like
5026 <p
><pre
>
5027 fastboot flash unlocktoken Unlock_code.bin
5028 </pre
></p
>
5030 <p
>And with that final step in place, the phone was unlocked and I
5031 could start stuffing the software of my own choosing into the device.
5032 So far I only inserted a replacement recovery image to wipe the phone
5033 before I start. We will see what happen next. Perhaps I should
5034 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
5039 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
5040 <link>https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
5041 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
5042 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
5043 <description><p
>For a while now, I have wanted to test
5044 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
5045 said to provide end to end encrypted communication and several of my
5046 friends and family are already using it. As I by choice do not own a
5047 mobile phone, this proved to be harder than expected. And I wanted to
5048 have the source of the client and know that it was the code used on my
5049 machine. But yesterday I managed to get it working. I used the
5050 Github source, compared it to the source in
5051 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
5052 Signal Chrome app
</a
> available from the Chrome web store, applied
5053 patches to use the production Signal servers, started the app and
5054 asked for the hidden
"register without a smart phone
" form. Here is
5055 the recipe how I did it.
</p
>
5057 <p
>First, I fetched the Signal desktop source from Github, using
5060 git clone https://github.com/WhisperSystems/Signal-Desktop.git
5063 <p
>Next, I patched the source to use the production servers, to be
5064 able to talk to other Signal users:
</p
>
5067 cat
&lt;
&lt;EOF | patch -p0
5068 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
5069 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
5070 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
5075 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
5076 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
5077 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
5078 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
5079 var messageReceiver;
5080 window.getSocketStatus = function() {
5081 if (messageReceiver) {
5082 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
5083 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
5084 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
5087 'use strict
';
5088 - var BUILD_EXPIRATION =
0;
5089 + var BUILD_EXPIRATION =
1474492690000;
5091 window.extension = window.extension || {};
5096 <p
>The first part is changing the servers, and the second is updating
5097 an expiration timestamp. This timestamp need to be updated regularly.
5098 It is set
90 days in the future by the build process (Gruntfile.js).
5099 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
5101 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
5102 script to launch Signal in Chromium.
</p
>
5109 --proxy-server=
"socks://localhost:
9050" \
5110 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
5113 <p
> The script start the app and configure Chromium to use the Tor
5114 SOCKS5 proxy to make sure those controlling the Signal servers (today
5115 Amazon and Whisper Systems) as well as those listening on the lines
5116 will have a harder time location my laptop based on the Signal
5117 connections if they use source IP address.
</p
>
5119 <p
>When the script starts, one need to follow the instructions under
5120 "Standalone Registration
" in the CONTRIBUTING.md file in the git
5121 repository. I right clicked on the Signal window to get up the
5122 Chromium debugging tool, visited the
'Console
' tab and wrote
5123 'extension.install(
"standalone
")
' on the console prompt to get the
5124 registration form. Then I entered by land line phone number and
5125 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
5126 repeated the verification code three times. After entering the number
5127 into the verification code field in the form, I could start using
5128 Signal from my laptop.
5130 <p
>As far as I can tell, The Signal app will leak who is talking to
5131 whom and thus who know who to those controlling the central server,
5132 but such leakage is hard to avoid with a centrally controlled server
5133 setup. It is something to keep in mind when using Signal - the
5134 content of your chats are harder to intercept, but the meta data
5135 exposing your contact network is available to people you do not know.
5136 So better than many options, but not great. And sadly the usage is
5137 connected to my land line, thus allowing those controlling the server
5138 to associate it to my home and person. I would prefer it if only
5139 those I knew could tell who I was on Signal. There are options
5140 avoiding such information leakage, but most of my friends are not
5141 using them, so I am stuck with Signal for now.
</p
>
5143 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
5145 <a href=
"https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
5146 and updated recipe for using the Signal app without a mobile
5147 phone
</a
>.
</p
>
5152 <title>The new
"best
" multimedia player in Debian?
</title>
5153 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
5154 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
5155 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
5156 <description><p
>When I set out a few weeks ago to figure out
5157 <a href=
"https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
5158 multimedia player in Debian claimed to support most file formats /
5159 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
5160 the various players claimed support for. The range was from
55 to
130
5161 MIME types. I suspect most media formats are supported by all
5162 players, but this is not really reflected in the MimeTypes values in
5163 their desktop files. There are probably also some bogus MIME types
5164 listed, but it is hard to identify which one this is.
</p
>
5166 <p
>Anyway, in the mean time I got in touch with upstream for some of
5167 the players suggesting to add more MIME types to their desktop files,
5168 and decided to spend some time myself improving the situation for my
5169 favorite media player VLC. The fixes for VLC entered Debian unstable
5170 yesterday. The complete list of MIME types can be seen on the
5171 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
5172 player MIME type support status
</a
> Debian wiki page.
</p
>
5174 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
5175 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
5176 kmplayer. I am sure some of the other players desktop files support
5177 several of the formats currently listed as working only with vlc,
5178 toten and parole.
</p
>
5180 <p
>A sad observation is that only
14 MIME types are listed as
5181 supported by all the tested multimedia players in Debian in their
5182 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
5183 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
5184 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
5185 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
5186 it sad that video/ogg and video/webm is not supported by all the media
5187 players in Debian. As far as I can tell, all of them can handle both
5193 <title>A program should be able to open its own files on Linux
</title>
5194 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
5195 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
5196 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
5197 <description><p
>Many years ago, when koffice was fresh and with few users, I
5198 decided to test its presentation tool when making the slides for a
5199 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
5200 wrote the first draft of the slides, saved the result and went to bed
5201 the day before I would give the talk. The next day I took a plane to
5202 the location where the meeting should take place, and on the plane I
5203 started up koffice again to polish the talk a bit, only to discover
5204 that kpresenter refused to load its own data file. I cursed a bit and
5205 started making the slides again from memory, to have something to
5206 present when I arrived. I tested that the saved files could be
5207 loaded, and the day seemed to be rescued. I continued to polish the
5208 slides until I suddenly discovered that the saved file could no longer
5209 be loaded into kpresenter. In the end I had to rewrite the slides
5210 three times, condensing the content until the talk became shorter and
5211 shorter. After the talk I was able to pinpoint the problem
&ndash;
5212 kpresenter wrote inline images in a way itself could not understand.
5213 Eventually that bug was fixed and kpresenter ended up being a great
5214 program to make slides. The point I
'm trying to make is that we
5215 expect a program to be able to load its own data files, and it is
5216 embarrassing to its developers if it can
't.
</p
>
5218 <p
>Did you ever experience a program failing to load its own data
5219 files from the desktop file browser? It is not a uncommon problem. A
5220 while back I discovered that the screencast recorder
5221 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
5222 browser would refuse to open. No video player claimed to understand
5223 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
5224 returning the application/ogg MIME type, which no video player I had
5225 installed listed as a MIME type they would understand. I asked for
5226 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
5227 behavour
</a
> and use the MIME type video/ogg instead. I also asked
5228 several video players to add video/ogg to their desktop files, to give
5229 the file browser an idea what to do about Ogg Theora files. After a
5230 while, the desktop file browsers in Debian started to handle the
5231 output from gtk-recordmydesktop properly.
</p
>
5233 <p
>But history repeats itself. A few days ago I tested the music
5234 system Rosegarden again, and I discovered that the KDE and xfce file
5235 browsers did not know what to do with the Rosegarden project files
5236 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
5237 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
5238 included in the next upload. To increase the chance of me remembering
5239 how to fix the problem next time some program fail to load its files
5240 from the file browser, here are some notes on how to fix it.
</p
>
5242 <p
>The file browsers in Debian in general operates on MIME types.
5243 There are two sources for the MIME type of a given file. The output from
5244 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
5245 shared MIME type registry (under /usr/share/mime/). The file MIME
5246 type is mapped to programs supporting the MIME type, and this
5247 information is collected from
5248 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
5249 desktop files
</a
> available in /usr/share/applications/. If there is
5250 one desktop file claiming support for the MIME type of the file, it is
5251 activated when asking to open a given file. If there are more, one
5252 can normally select which one to use by right-clicking on the file and
5253 selecting the wanted one using
'Open with
' or similar. In general
5254 this work well. But it depend on each program picking a good MIME
5256 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
5257 MIME type registered with IANA
</a
>), file and/or the shared MIME
5258 registry recognizing the file and the desktop file to list the MIME
5259 type in its list of supported MIME types.
</p
>
5261 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
5262 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
5263 Shared MIME database
</a
> look like this:
</p
>
5265 <p
><blockquote
><pre
>
5266 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
5267 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
5268 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
5269 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
5270 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
5271 &lt;glob pattern=
"*.rg
"/
&gt;
5272 &lt;/mime-type
&gt;
5273 &lt;/mime-info
&gt;
5274 </pre
></blockquote
></p
>
5276 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
5277 (it is a gzipped XML file). Note, it is much better to use an
5278 official MIME type registered with IANA than it is to make up ones own
5279 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
5281 <p
>The desktop file of the rosegarden program failed to list
5282 audio/x-rosegarden in its list of supported MIME types, causing the
5283 file browsers to have no idea what to do with *.rg files:
</p
>
5285 <p
><blockquote
><pre
>
5286 % grep Mime /usr/share/applications/rosegarden.desktop
5287 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
5288 X-KDE-NativeMimeType=audio/x-rosegarden-composition
5290 </pre
></blockquote
></p
>
5292 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
5293 MimeType= line.
</p
>
5295 <p
>If you run into a file which fail to open the correct program when
5296 selected from the file browser, please check out the output from
5297 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
5298 MIME type is registered somewhere under /usr/share/mime/ and check
5299 that some desktop file under /usr/share/applications/ is claiming
5300 support for this MIME type. If not, please report a bug to have it
5306 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
5307 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
5308 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
5309 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
5310 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
5311 system
</a
> is a user-focused solution in Debian for handling hardware
5312 related packages. The idea is to have a database of mappings between
5313 hardware and packages, and pop up a dialog suggesting for the user to
5314 install the packages to use a given hardware dongle. Some use cases
5315 are when you insert a Yubikey, it proposes to install the software
5316 needed to control it; when you insert a braille reader list it
5317 proposes to install the packages needed to send text to the reader;
5318 and when you insert a ColorHug screen calibrator it suggests to
5319 install the driver for it. The system work well, and even have a few
5320 command line tools to install firmware packages and packages for the
5321 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
5323 <p
>The system was initially written using aptdaemon, because I found
5324 good documentation and example code on how to use it. But aptdaemon
5325 is going away and is generally being replaced by
5326 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
5327 so Isenkram needed a rewrite. And today, thanks to the great patch
5328 from my college Sunil Mohan Adapa in the FreedomBox project, the
5329 rewrite finally took place. I
've just uploaded a new version of
5330 Isenkram into Debian Unstable with the patch included, and the default
5331 for the background daemon is now to use PackageKit. To check it out,
5332 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
5333 and see if it is recognised.
</p
>
5335 <p
>If you want to know what kind of packages isenkram would propose for
5336 the machine it is running on, you can check out the isenkram-lookup
5337 program. This is what it look like on a Thinkpad X230:
</p
>
5339 <p
><blockquote
><pre
>
5355 </pre
></blockquote
></p
>
5357 <p
>The hardware mappings come from several places. The preferred way
5358 is for packages to announce their hardware support using
5359 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
5360 cross distribution appstream system
</a
>.
5362 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
5363 blog posts about isenkram
</a
> to learn how to do that.
</p
>
5368 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
5369 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
5370 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
5371 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
5372 <description><p
>Yesterday I updated the
5373 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
5374 package in Debian
</a
> with a few patches sent to me by skilled and
5375 enterprising users. There were some nice user and visible changes.
5376 First of all, both desktop menu entries now work. A design flaw in
5377 one of the script made the history graph fail to show up (its PNG was
5378 dumped in ~/.xsession-errors) if no controlling TTY was available.
5379 The script worked when called from the command line, but not when
5380 called from the desktop menu. I changed this to look for a DISPLAY
5381 variable or a TTY before deciding where to draw the graph, and now the
5382 graph window pop up as expected.
</p
>
5384 <p
>The next new feature is a discharge rate estimator in one of the
5385 graphs (the one showing the last few hours). New is also the user of
5386 colours showing charging in blue and discharge in red. The percentages
5387 of this graph is relative to last full charge, not battery design
5390 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
5392 <p
>The other graph show the entire history of the collected battery
5393 statistics, comparing it to the design capacity of the battery to
5394 visualise how the battery life time get shorter over time. The red
5395 line in this graph is what the previous graph considers
100 percent:
5397 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
5399 <p
>In this graph you can see that I only charge the battery to
80
5400 percent of last full capacity, and how the capacity of the battery is
5401 shrinking. :(
</p
>
5403 <p
>The last new feature is in the collector, which now will handle
5404 more hardware models. On some hardware, Linux power supply
5405 information is stored in /sys/class/power_supply/ACAD/, while the
5406 collector previously only looked in /sys/class/power_supply/AC/. Now
5407 both are checked to figure if there is power connected to the
5410 <p
>If you are interested in how your laptop battery is doing, please
5412 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
5413 in Debian unstable, or rebuild it on Jessie to get it working on
5414 Debian stable. :) The upstream source is available from
<a
5415 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5416 Patches are very welcome.
</p
>
5418 <p
>As usual, if you use Bitcoin and want to show your support of my
5419 activities, please send Bitcoin donations to my address
5420 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5425 <title>Debian now with ZFS on Linux included
</title>
5426 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
5427 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
5428 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
5429 <description><p
>Today, after many years of hard work from many people,
5430 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
5431 Debian. The package status can be seen on
5432 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
5433 for zfs-linux
</a
>. and
5434 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
5435 team status page
</a
>. If you want to help out, please join us.
5436 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
5437 source code
</a
> is available via git on Alioth. It would also be
5438 great if you could help out with
5439 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
5440 it is an important piece of the puzzle to get ZFS working.
</p
>
5445 <title>What is the best multimedia player in Debian?
</title>
5446 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
5447 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
5448 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
5449 <description><p
><strong
>Where I set out to figure out which multimedia player in
5450 Debian claim support for most file formats.
</strong
></p
>
5452 <p
>A few years ago, I had a look at the media support for Browser
5453 plugins in Debian, to get an idea which plugins to include in Debian
5454 Edu. I created a script to extract the set of supported MIME types
5455 for each plugin, and used this to find out which multimedia browser
5456 plugin supported most file formats / media types.
5457 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
5458 result
</a
> can still be seen on the Debian wiki, even though it have
5459 not been updated for a while. But browser plugins are less relevant
5460 these days, so I thought it was time to look at standalone
5463 <p
>A few days ago I was tired of VLC not being listed as a viable
5464 player when I wanted to play videos from the Norwegian National
5465 Broadcasting Company, and decided to investigate why. The cause is a
5466 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
5467 desktop file
</a
>. In the process I wrote a script to compare the set
5468 of MIME types announced in the desktop file and the browser plugin,
5469 only to discover that there is quite a large difference between the
5470 two for VLC. This discovery made me dig up the script I used to
5471 compare browser plugins, and adjust it to compare desktop files
5472 instead, to try to figure out which multimedia player in Debian
5473 support most file formats.
</p
>
5475 <p
>The result can be seen on the Debian Wiki, as
5476 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
5477 table listing all MIME types supported by one of the packages included
5478 in the table
</a
>, with the package supporting most MIME types being
5479 listed first in the table.
</p
>
5481 </p
>The best multimedia player in Debian? It is totem, followed by
5482 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
5483 kmplayer. Time for the other players to update their announced MIME
5489 <title>The Pyra - handheld computer with Debian preinstalled
</title>
5490 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
5491 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
5492 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
5493 <description>A friend of mine made me aware of
5494 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
5495 handheld computer which will be delivered with Debian preinstalled. I
5496 would love to get one of those for my birthday. :)
</p
>
5498 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
5499 plugs and many others connectors, and include a full keyboard and a
5"
5500 LCD touch screen. The
6000mAh battery is claimed to provide a whole
5501 day of battery life time, but I have not seen any independent tests
5502 confirming this. The vendor is still collecting preorders, and the
5503 last I heard last night was that
22 more orders were needed before
5504 production started.
</p
>
5506 <p
>As far as I know, this is the first handheld preinstalled with
5507 Debian. Please let me know if you know of any others. Is it the
5508 first computer being sold with Debian preinstalled?
</p
>
5513 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
5514 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
5515 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
5516 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
5517 <description><p
>During this weekends
5518 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
5519 squashing party and developer gathering
</a
>, we decided to do our part
5520 to make sure there are good books about Debian available in Norwegian
5521 Bokmål, and got in touch with the people behind the
5522 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
5523 project
</a
> to get started. If you want to help out, please start
5525 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
5526 hosted weblate project page
</a
>, and get in touch using
5527 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
5528 translators mailing list
</a
>. Please also check out
5529 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
5530 contributors
</a
>.
</p
>
5532 <p
>The book is already available on paper in English, French and
5533 Japanese, and our goal is to get it available on paper in Norwegian
5534 Bokmål too. In addition to the paper edition, there are also EPUB and
5535 Mobi versions available. And there are incomplete translations
5536 available for many more languages.
</p
>
5541 <title>One in two hundred Debian users using ZFS on Linux?
</title>
5542 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
5543 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
5544 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
5545 <description><p
>Just for fun I had a look at the popcon number of ZFS related
5546 packages in Debian, and was quite surprised with what I found. I use
5547 ZFS myself at home, but did not really expect many others to do so.
5548 But I might be wrong.
</p
>
5550 <p
>According to
5551 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
5552 results for spl-linux
</a
>, there are
1019 Debian installations, or
5553 0.53% of the population, with the package installed. As far as I know
5554 the only use of the spl-linux package is as a support library for ZFS
5555 on Linux, so I use it here as proxy for measuring the number of ZFS
5556 installation on Linux in Debian. In the kFreeBSD variant of Debian
5557 the ZFS feature is already available, and there
5558 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
5559 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
5560 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
5562 <p
>But even though the Debian project leader Lucas Nussbaum
5563 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
5564 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
5565 cleared, the package is still not in Debian. The package is again in
5566 the NEW queue. Several uploads have been rejected so far because the
5567 debian/copyright file was incomplete or wrong, but there is no reason
5568 to give up. The current status can be seen on
5569 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
5570 team status page
</a
>, and
5571 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
5572 source code
</a
> is available on Alioth.
</p
>
5574 <p
>As I want ZFS to be included in next version of Debian to make sure
5575 my home server can function in the future using only official Debian
5576 packages, and the current blocker is to get the debian/copyright file
5577 accepted by the FTP masters in Debian, I decided a while back to try
5578 to help out the team. This was the background for my blog post about
5579 <a href=
"https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
5580 updating and checking debian/copyright semi-automatically
</a
>, and I
5581 used the techniques I explored there to try to find any errors in the
5582 copyright file. It is not very easy to check every one of the around
5583 2000 files in the source package, but I hope we this time got it
5584 right. If you want to help out, check out the git source and try to
5585 find missing entries in the debian/copyright file.
</p
>
5590 <title>Full battery stats collector is now available in Debian
</title>
5591 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
5592 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
5593 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
5594 <description><p
>Since this morning, the battery-stats package in Debian include an
5595 extended collector that will collect the complete battery history for
5596 later processing and graphing. The original collector store the
5597 battery level as percentage of last full level, while the new
5598 collector also record battery vendor, model, serial number, design
5599 full level, last full level and current battery level. This make it
5600 possible to predict the lifetime of the battery as well as visualise
5601 the energy flow when the battery is charging or discharging.
</p
>
5603 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
5604 in the version
0.5.1 package in unstable. Get the new battery level graph
5605 and lifetime prediction by running:
5607 <p
><pre
>
5608 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
5609 </pre
></p
>
5611 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
5613 <p
>The flow in/out of the battery can be seen by running (no menu
5614 entry yet):
</p
>
5616 <p
><pre
>
5617 /usr/share/battery-stats/battery-stats-graph-flow
5618 </pre
></p
>
5620 <p
>I
'm not quite happy with the way the data is visualised, at least
5621 when there are few data points. The graphs look a bit better with a
5622 few years of data.
</p
>
5624 <p
>A while back one important feature I use in the battery stats
5625 collector broke in Debian. The scripts in
5626 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
5627 suspect it happened when Jessie started using systemd, but I do not
5628 know. The issue is reported as
5629 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
5630 pm-utils. I managed to work around it by adding an udev rule to call
5631 the collector script every time the power connector is connected and
5632 disconnected. With this fix in place it was finally time to make a
5633 new release of the package, and get it into Debian.
</p
>
5635 <p
>If you are interested in how your laptop battery is doing, please
5637 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
5638 in Debian unstable, or rebuild it on Jessie to get it working on
5639 Debian stable. :) The upstream source is available from
5640 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5641 As always, patches are very welcome.
</p
>
5646 <title>Making battery measurements a little easier in Debian
</title>
5647 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
5648 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
5649 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
5650 <description><p
>Back in September, I blogged about
5651 <a href=
"https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
5652 system I wrote to collect statistics about my laptop battery
</a
>, and
5653 how it showed the decay and death of this battery (now replaced). I
5654 created a simple deb package to handle the collection and graphing,
5655 but did not want to upload it to Debian as there were already
5656 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
5657 package in Debian
</a
> that should do the same thing, and I did not see
5658 a point of uploading a competing package when battery-stats could be
5659 fixed instead. I reported a few bugs about its non-function, and
5660 hoped someone would step in and fix it. But no-one did.
</p
>
5662 <p
>I got tired of waiting a few days ago, and took matters in my own
5663 hands. The end result is that I am now the new upstream developer of
5664 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
5665 battery-stats in Debian, and the package in Debian unstable is finally
5666 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
5667 information provided by the Linux kernel. If you install the
5668 battery-stats package from unstable now, you will be able to get a
5669 graph of the current battery fill level, to get some idea about the
5670 status of the battery. The source package build and work just fine in
5671 Debian testing and stable (and probably oldstable too, but I have not
5672 tested). The default graph you get for that system look like this:
</p
>
5674 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
5676 <p
>My plans for the future is to merge my old scripts into the
5677 battery-stats package, as my old scripts collected a lot more details
5678 about the battery. The scripts are merged into the upstream
5679 battery-stats git repository already, but I am not convinced they work
5680 yet, as I changed a lot of paths along the way. Will have to test a
5681 bit more before I make a new release.
</p
>
5683 <p
>I will also consider changing the file format slightly, as I
5684 suspect the way I combine several values into one field might make it
5685 impossible to know the type of the value when using it for processing
5686 and graphing.
</p
>
5688 <p
>If you would like I would like to keep an close eye on your laptop
5689 battery, check out the battery-stats package in
5690 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
5692 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5693 I would love some help to improve the system further.
</p
>
5698 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
5699 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
5700 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
5701 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
5702 <description><p
>Making packages for Debian requires quite a lot of attention to
5703 details. And one of the details is the content of the
5704 debian/copyright file, which should list all relevant licenses used by
5705 the code in the package in question, preferably in
5706 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
5707 readable DEP5 format
</a
>.
</p
>
5709 <p
>For large packages with lots of contributors it is hard to write
5710 and update this file manually, and if you get some detail wrong, the
5711 package is normally rejected by the ftpmasters. So getting it right
5712 the first time around get the package into Debian faster, and save
5713 both you and the ftpmasters some work.. Today, while trying to figure
5714 out what was wrong with
5715 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
5716 zfsonlinux copyright file
</a
>, I decided to spend some time on
5717 figuring out the options for doing this job automatically, or at least
5718 semi-automatically.
</p
>
5720 <p
>Lucikly, there are at least two tools available for generating the
5721 file based on the code in the source package,
5722 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
5723 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
5724 not sure which one of them came first, but both seem to be able to
5725 create a sensible draft file. As far as I can tell, none of them can
5726 be trusted to get the result just right, so the content need to be
5727 polished a bit before the file is OK to upload. I found the debmake
5729 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
5730 blog posts from
2014</a
>.
5732 <p
>To generate using debmake, use the -cc option:
5734 <p
><pre
>
5735 debmake -cc
> debian/copyright
5736 </pre
></p
>
5738 <p
>Note there are some problems with python and non-ASCII names, so
5739 this might not be the best option.
</p
>
5741 <p
>The cme option is based on a config parsing library, and I found
5743 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
5744 blog post from
2015</a
>. To generate using cme, use the
'update
5745 dpkg-copyright
' option:
5747 <p
><pre
>
5748 cme update dpkg-copyright
5749 </pre
></p
>
5751 <p
>This will create or update debian/copyright. The cme tool seem to
5752 handle UTF-
8 names better than debmake.
</p
>
5754 <p
>When the copyright file is created, I would also like some help to
5755 check if the file is correct. For this I found two good options,
5756 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
5757 to focus on license types and file matching, and is able to detect
5758 ineffective blocks in the copyright file. The latter reports missing
5759 copyright holders and years, but was confused by inconsistent license
5760 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
5761 fix all issues reported by them before uploading. But I do not know
5762 if the tools and the ftpmasters agree on what is important to fix in a
5763 copyright file, so the package might still be rejected.
</p
>
5765 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
5766 will read through the source and try to find all copyright statements.
5767 It is not comparing the result to the content of debian/copyright, but
5768 can be useful when verifying the content of the copyright file.
</p
>
5770 <p
>Are you aware of better tools in Debian to create and update
5771 debian/copyright file. Please let me know, or blog about it on
5772 planet.debian.org.
</p
>
5774 <p
>As usual, if you use Bitcoin and want to show your support of my
5775 activities, please send Bitcoin donations to my address
5776 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5778 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
5779 on how to use licensecheck and cdbs to create a draft copyright file
5781 <p
><pre
>
5782 licensecheck --copyright -r `find * -type f` | \
5783 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
5784 </pre
></p
>
5786 <p
>He mentioned that he normally check the generated file into the
5787 version control system to make it easier to discover license and
5788 copyright changes in the upstream source. I will try to do the same
5789 with my packages in the future.
</p
>
5791 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
5792 against using -quiet for new users, so I removed it from the proposed
5793 command line.
</p
>
5798 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
5799 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
5800 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
5801 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
5802 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
5803 is taking shape in Debian, and one provided feature is a very
5804 convenient way to tell you which package to install to make a given
5805 firmware file available when the kernel is looking for it. This can
5806 be done using apt-file too, but that is for someone else to blog
5809 <p
>Here is a small recipe to find the package with a given firmware
5810 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
5811 picked from the set of firmware announced using appstream in Debian
5812 unstable. In general you would be looking for the firmware requested
5813 by the kernel during kernel module loading. To find the package
5814 providing the example file, do like this:
</p
>
5816 <blockquote
><pre
>
5817 % apt install appstream
5821 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
5822 awk
'/Package:/ {print $
2}
'
5825 </pre
></blockquote
>
5827 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
5828 appstream wiki
</a
> page to learn how to embed the package metadata in
5829 a way appstream can use.
</p
>
5831 <p
>This same approach can be used to find any package supporting a
5832 given MIME type. This is very useful when you get a file you do not
5833 know how to handle. First find the mime type using
<tt
>file
5834 --mime-type
</tt
>, and next look up the package providing support for
5835 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
5836 and you can find all packages handling this type like this:
</p
>
5838 <blockquote
><pre
>
5839 % apt install appstream
5843 % appstreamcli what-provides mimetype image/svg+xml | \
5844 awk
'/Package:/ {print $
2}
'
5866 </pre
></blockquote
>
5868 <p
>I believe the MIME types are fetched from the desktop file for
5869 packages providing appstream metadata.
</p
>
5874 <title>Creepy, visualise geotagged social media information - nice free software
</title>
5875 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
5876 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
5877 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
5878 <description><p
>Most people seem not to realise that every time they walk around
5879 with the computerised radio beacon known as a mobile phone their
5880 position is tracked by the phone company and often stored for a long
5881 time (like every time a SMS is received or sent). And if their
5882 computerised radio beacon is capable of running programs (often called
5883 mobile apps) downloaded from the Internet, these programs are often
5884 also capable of tracking their location (if the app requested access
5885 during installation). And when these programs send out information to
5886 central collection points, the location is often included, unless
5887 extra care is taken to not send the location. The provided
5888 information is used by several entities, for good and bad (what is
5889 good and bad, depend on your point of view). What is certain, is that
5890 the private sphere and the right to free movement is challenged and
5891 perhaps even eradicated for those announcing their location this way,
5892 when they share their whereabouts with private and public
5895 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
5897 <p
>The phone company logs provide a register of locations to check out
5898 when one want to figure out what the tracked person was doing. It is
5899 unavailable for most of us, but provided to selected government
5900 officials, company staff, those illegally buying information from
5901 unfaithful servants and crackers stealing the information. But the
5902 public information can be collected and analysed, and a free software
5903 tool to do so is called
5904 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
5905 discovered it when I read
5906 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
5907 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
5908 November
2014, and decided to check if it was available in Debian.
5909 The python program was in Debian, but
5910 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
5911 Debian
</a
> was completely broken and practically unmaintained. I
5912 uploaded a new version which did not work quite right, but did not
5913 have time to fix it then. This Christmas I decided to finally try to
5914 get Creepy operational in Debian. Now a fixed version is available in
5915 Debian unstable and testing, and almost all Debian specific patches
5917 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
5919 <p
>The Creepy program visualises geolocation information fetched from
5920 Twitter, Instagram, Flickr and Google+, and allow one to get a
5921 complete picture of every social media message posted recently in a
5922 given area, or track the movement of a given individual across all
5923 these services. Earlier it was possible to use the search API of at
5924 least some of these services without identifying oneself, but these
5925 days it is impossible. This mean that to use Creepy, you need to
5926 configure it to log in as yourself on these services, and provide
5927 information to them about your search interests. This should be taken
5928 into account when using Creepy, as it will also share information
5929 about yourself with the services.
</p
>
5931 <p
>The picture above show the twitter messages sent from (or at least
5932 geotagged with a position from) the city centre of Oslo, the capital
5933 of Norway. One useful way to use Creepy is to first look at
5934 information tagged with an area of interest, and next look at all the
5935 information provided by one or more individuals who was in the area.
5936 I tested it by checking out which celebrity provide their location in
5937 twitter messages by checkout out who sent twitter messages near a
5938 Norwegian TV station, and next could track their position over time,
5939 making it possible to locate their home and work place, among other
5940 things. A similar technique have been
5941 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
5942 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
5943 tool to discover lying governments, and a useful tool to help people
5944 understand the value of the private information they provide to the
5947 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
5948 it depend on several python modules currently missing in Jessie (at
5949 least python-instagram, python-flickrapi and
5950 python-requests-toolbelt).
</p
>
5952 <p
>(I have uploaded
5953 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
5954 screenshots.debian.net
</a
> and licensed it under the same terms as the
5955 Creepy program in Debian.)
</p
>
5960 <title>Always download Debian packages using Tor - the simple recipe
</title>
5961 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
5962 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
5963 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
5964 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
5965 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
5966 that those listening on the Internet lines would have good reason to
5967 believe a computer have a given security hole
</a
> if it download a
5968 security fix from a Debian mirror. This is a good reason to always
5969 use encrypted connections to the Debian mirror, to make sure those
5970 listening do not know which IP address to attack. In August, Richard
5971 Hartmann observed that encryption was not enough, when it was possible
5972 to interfere download size to security patches or the fact that
5973 download took place shortly after a security fix was released, and
5974 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
5975 to always use Tor to download packages from the Debian mirror
</a
>. He
5976 was not the first to propose this, as the
5977 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
5978 package by Tim Retout already existed to make it easy to convince apt
5979 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
5980 aware of that package when I read the blog post from Richard.
</p
>
5982 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
5983 sysadmins, and he set up a Tor hidden service on one of the central
5984 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
5985 it possible to download packages directly between two tor nodes,
5986 making sure the network traffic always were encrypted.
</p
>
5988 <p
>Here is a short recipe for enabling this on your machine, by
5989 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
5990 urls with tor+http and tor+https, and using the hidden service instead
5991 of the official Debian mirror site. I recommend installing
5992 <tt
>etckeeper
</tt
> before you start to have a history of the changes
5993 done in /etc/.
</p
>
5995 <blockquote
><pre
>
5996 apt install apt-transport-tor
5997 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
5998 sed -i
's% http% tor+http%
' /etc/apt/sources.list
5999 </pre
></blockquote
>
6001 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
6002 the sed commands for these too. The sed command is assuming your are
6003 using the ftp.debian.org Debian mirror. Adjust the command (or just
6004 edit the file manually) to match your mirror.
</p
>
6006 <p
>This work in Debian Jessie and later. Note that tools like
6007 <tt
>apt-file
</tt
> only recently started using the apt transport
6008 system, and do not work with these tor+http URLs. For
6009 <tt
>apt-file
</tt
> you need the version currently in experimental,
6010 which need a recent apt version currently only in unstable. So if you
6011 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
6013 <p
>Another advantage from this change is that your machine will start
6014 using Tor regularly and at fairly random intervals (every time you
6015 update the package lists or upgrade or install a new package), thus
6016 masking other Tor traffic done from the same machine. Using Tor will
6017 become normal for the machine in question.
</p
>
6019 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
6020 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
6021 enabled. It would be great if it was the default on any Debian
6027 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
6028 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
6029 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
6030 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
6031 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
6032 call the car license plate numbers in those days. I would write the
6033 numbers down in my little book and compare notes with the other kids
6034 to see how many region codes we had seen and if we had seen some
6035 exotic or special region codes and numbers. It was a fun game to pass
6036 time, as we kids have plenty of it.
</p
>
6038 <p
>A few days I came across
6039 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
6040 project
</a
>, a free software project to automatically discover and
6041 report license plates in images and video streams, and provide the
6042 "car numbers
" in a machine readable format. I
've been looking for
6043 such system for a while now, because I believe it is a bad idea that the
6044 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
6045 number plate recognition
</a
> tool only is available in the hands of
6046 the powerful, and want it to be available also for the powerless to
6047 even the score when it comes to surveillance and sousveillance. I
6048 discovered the developer
6049 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
6050 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
6051 help him get it into shape to get the package uploaded into the Debian
6054 <p
>Today we finally managed to get the package into shape and uploaded
6055 it into Debian, where it currently
6056 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
6057 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
6059 <p
>I guess you are wondering why on earth such tool would be useful
6060 for the common folks, ie those not running a large government
6061 surveillance system? Well, I plan to put it in a computer on my bike
6062 and in my car, tracking the cars nearby and allowing me to be notified
6063 when number plates on my watch list are discovered. Another use case
6064 was suggested by a friend of mine, who wanted to set it up at his home
6065 to open the car port automatically when it discovered the plate on his
6066 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
6067 capable of placing his license plate number of a piece of cardboard to
6068 open his car port, men replied that it was always unlocked anyway. I
6069 guess for such use case it make sense. I am sure there are other use
6070 cases too, for those with imagination and a vision.
</p
>
6072 <p
>If you want to build your own version of the Debian package, check
6073 out the upstream git source and symlink ./distros/debian to ./debian/
6074 before running
"debuild
" to build the source. Or wait a bit until the
6075 package show up in unstable.
</p
>
6080 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
6081 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
6082 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
6083 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
6084 <description><p
>Around three years ago, I created
6085 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
6086 system
</a
> to get a more practical solution in Debian for handing
6087 hardware related packages. A GUI system in the isenkram package will
6088 present a pop-up dialog when some hardware dongle supported by
6089 relevant packages in Debian is inserted into the machine. The same
6090 lookup mechanism to detect packages is available as command line
6091 tools in the isenkram-cli package. In addition to mapping hardware,
6092 it will also map kernel firmware files to packages and make it easy to
6093 install needed firmware packages automatically. The key for this
6094 system to work is a good way to map hardware to packages, in other
6095 words, allow packages to announce what hardware they will work
6098 <p
>I started by providing data files in the isenkram source, and
6099 adding code to download the latest version of these data files at run
6100 time, to ensure every user had the most up to date mapping available.
6101 I also added support for storing the mapping in the Packages file in
6102 the apt repositories, but did not push this approach because while I
6103 was trying to figure out how to best store hardware/package mappings,
6104 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
6105 appstream system
</a
> was announced. I got in touch and suggested to
6106 add the hardware mapping into that data set to be able to use
6107 appstream as a data source, and this was accepted at least for the
6108 Debian version of appstream.
</p
>
6110 <p
>A few days ago using appstream in Debian for this became possible,
6111 and today I uploaded a new version
0.20 of isenkram adding support for
6112 appstream as a data source for mapping hardware to packages. The only
6113 package so far using appstream to announce its hardware support is my
6114 pymissile package. I got help from Matthias Klumpp with figuring out
6115 how do add the required
6116 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
6117 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
6118 this content:
</p
>
6120 <blockquote
><pre
>
6121 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
6122 &lt;component
&gt;
6123 &lt;id
&gt;pymissile
&lt;/id
&gt;
6124 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
6125 &lt;name
&gt;pymissile
&lt;/name
&gt;
6126 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
6127 &lt;description
&gt;
6129 Pymissile provides a curses interface to control an original
6130 Marks and Spencer / Striker USB Missile Launcher, as well as a
6131 motion control script to allow a webcamera to control the
6134 &lt;/description
&gt;
6135 &lt;provides
&gt;
6136 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
6137 &lt;/provides
&gt;
6138 &lt;/component
&gt;
6139 </pre
></blockquote
>
6141 <p
>The key for isenkram is the component/provides/modalias value,
6142 which is a glob style match rule for hardware specific strings
6143 (modalias strings) provided by the Linux kernel. In this case, it
6144 will map to all USB devices with vendor code
1130 and product code
6147 <p
>Note, it is important that the license of all the metadata files
6148 are compatible to have permissions to aggregate them into archive wide
6149 appstream files. Matthias suggested to use MIT or BSD licenses for
6150 these files. A challenge is figuring out a good id for the data, as
6151 it is supposed to be globally unique and shared across distributions
6152 (in other words, best to coordinate with upstream what to use). But
6153 it can be changed later or, so we went with the package name as
6154 upstream for this project is dormant.
</p
>
6156 <p
>To get the metadata file installed in the correct location for the
6157 mirror update scripts to pick it up and include its content the
6158 appstream data source, the file must be installed in the binary
6159 package under /usr/share/appdata/. I did this by adding the following
6160 line to debian/pymissile.install:
</p
>
6162 <blockquote
><pre
>
6163 debian/pymissile.metainfo.xml usr/share/appdata
6164 </pre
></blockquote
>
6166 <p
>With that in place, the command line tool isenkram-lookup will list
6167 all packages useful on the current computer automatically, and the GUI
6168 pop-up handler will propose to install the package not already
6169 installed if a hardware dongle is inserted into the machine in
6172 <p
>Details of the modalias field in appstream is available from the
6173 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
6175 <p
>To locate the modalias values of all hardware present in a machine,
6176 try running this command on the command line:
</p
>
6178 <blockquote
><pre
>
6179 cat $(find /sys/devices/|grep modalias)
6180 </pre
></blockquote
>
6182 <p
>To learn more about the isenkram system, please check out
6183 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">my
6184 blog posts tagged isenkram
</a
>.
</p
>
6189 <title>The GNU General Public License is not magic pixie dust
</title>
6190 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
6191 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
6192 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
6193 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
6194 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
6195 GPL is not magic pixie dust
</a
>" explain the importance of making sure
6196 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
6197 I quote the blog post from Paul in full here with his permission:
<p
>
6201 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
6204 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
6206 The first step is to choose a
6207 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
6210 The next step is, when someone fails to follow that copyleft license,
6211 <b
>it must be enforced
</b
><br/
>
6213 and its a simple fact of our modern society that such type of
6216 is incredibly expensive to do and incredibly difficult to do.
6219 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
6220 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
6221 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
6222 0x57</a
></small
></p
>
6224 <p
>As the Debian Website
6225 <a href=
"https://bugs.debian.org/
794116">used
</a
>
6226 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
6227 imply, public domain and permissively licensed software can lead to
6228 the production of more proprietary software as people discover useful
6229 software, extend it and or incorporate it into their hardware or
6230 software products. Copyleft licenses such as the GNU GPL were created
6231 to close off this avenue to the production of proprietary software but
6232 such licenses are not enough. With the ongoing adoption of Free
6233 Software by individuals and groups, inevitably the community
's
6234 expectations of license compliance are violated, usually out of
6235 ignorance of the way Free Software works, but not always. As Karen
6236 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
6237 Freedom
">FaiF
</a
>
6238 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
6239 copyleft is nothing if no-one is willing and able to stand up in court
6240 to protect it. The reality of today
's world is that legal
6241 representation is expensive, difficult and time consuming. With
6242 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
6243 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
6244 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
6245 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
6246 of the Linux project, Debian and other groups against GPL violations.
6247 In March the SFC supported a
6248 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
6249 by Christoph Hellwig
</a
> against VMware for refusing to
6250 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
6251 with the GPL
</a
> in relation to their use of parts of the Linux
6252 kernel. Since then two of their sponsors pulled corporate funding and
6254 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
6255 or cancelled their talks
</a
>. As a result they have decided to rely
6256 less on corporate funding and more on the broad community of
6257 individuals who support Free Software and copyleft. So the SFC has
6258 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
6259 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
6260 a community of folks who stand up for copyleft and the GPL by
6261 supporting their work on promoting and supporting copyleft and Free
6264 <p
>If you support Free Software,
6265 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
6266 what the SFC do, agree with their
6267 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
6268 principles
</a
>, are happy about their
6269 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
6270 work on a project that is an SFC
6271 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
6272 just want to stand up for copyleft, please join
6273 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
6274 Allan Webber
</a
>,
6275 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
6277 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
6278 Bacon
</a
>, myself and
6279 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
6281 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
6282 next week your donation will be
6283 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
6284 by an anonymous donor. Please also consider asking your employer to
6285 match your donation or become a sponsor of SFC. Don
't forget to
6286 spread the word about your support for SFC via email, your blog and or
6287 social media accounts.
</p
>
6291 <p
>I agree with Paul on this topic and just signed up as a Supporter
6292 of Software Freedom Conservancy myself. Perhaps you should be a
6293 supporter too?
</p
>
6298 <title>PGP key transition statement for key EE4E02F9
</title>
6299 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
6300 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
6301 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
6302 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
6303 set it up properly. I wanted to generate it offline and have it
6304 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
6305 smart card
</a
> for daily use, and learning how to do it and finding
6306 time to sit down with an offline machine almost took forever. But
6307 finally I
've been able to complete the process, and have now moved
6308 from my old GPG key to a new GPG key. See
6309 <a href=
"https://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
6310 full transition statement, signed with both my old and new key
</a
> for
6311 the details. This is my new key:
</p
>
6314 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
6315 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
6316 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
6317 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
6318 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
6319 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
6320 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
6323 <p
>The key can be downloaded from the OpenPGP key servers, signed by
6324 my old key.
</p
>
6326 <p
>If you signed my old key
6327 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
6328 I
'd very much appreciate a signature on my new key, details and
6329 instructions in the transition statement. I m happy to reciprocate if
6330 you have a similarly signed transition statement to present.
</p
>
6335 <title>The life and death of a laptop battery
</title>
6336 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
6337 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
6338 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
6339 <description><p
>When I get a new laptop, the battery life time at the start is OK.
6340 But this do not last. The last few laptops gave me a feeling that
6341 within a year, the life time is just a fraction of what it used to be,
6342 and it slowly become painful to use the laptop without power connected
6343 all the time. Because of this, when I got a new Thinkpad X230 laptop
6344 about two years ago, I decided to monitor its battery state to have
6345 more hard facts when the battery started to fail.
</p
>
6347 <img src=
"https://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
6349 <p
>First I tried to find a sensible Debian package to record the
6350 battery status, assuming that this must be a problem already handled
6351 by someone else. I found
6352 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
6353 which collects statistics from the battery, but it was completely
6354 broken. I sent a few suggestions to the maintainer, but decided to
6355 write my own collector as a shell script while I waited for feedback
6357 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
6358 blog post about the battery development on a MacBook Air
</a
> I also
6360 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
6361 available in Debian.
</p
>
6363 <p
>I started my collector
2013-
07-
15, and it has been collecting
6364 battery stats ever since. Now my
6365 /var/log/hjemmenett-battery-status.log file contain around
115,
000
6366 measurements, from the time the battery was working great until now,
6367 when it is unable to charge above
7% of original capacity. My
6368 collector shell script is quite simple and look like this:
</p
>
6373 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
6375 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
6376 logfile=/var/log/hjemmenett-battery-status.log
6378 files=
"manufacturer model_name technology serial_number \
6379 energy_full energy_full_design energy_now cycle_count status
"
6381 if [ ! -e
"$logfile
" ] ; then
6383 printf
"timestamp,
"
6385 printf
"%s,
" $f
6388 )
> "$logfile
"
6392 # Print complete message in one echo call, to avoid race condition
6393 # when several log processes run in parallel.
6394 msg=$(printf
"%s,
" $(date +%s); \
6395 for f in $files; do \
6396 printf
"%s,
" $(cat $f); \
6398 echo
"$msg
"
6401 cd /sys/class/power_supply
6404 (cd $bat
&& log_battery
>> "$logfile
")
6408 <p
>The script is called when the power management system detect a
6409 change in the power status (power plug in or out), and when going into
6410 and out of hibernation and suspend. In addition, it collect a value
6411 every
10 minutes. This make it possible for me know when the battery
6412 is discharging, charging and how the maximum charge change over time.
6413 The code for the Debian package
6414 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
6415 available on github
</a
>.
</p
>
6417 <p
>The collected log file look like this:
</p
>
6420 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
6421 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
6423 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
6424 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
6427 <p
>I wrote a small script to create a graph of the charge development
6428 over time. This graph depicted above show the slow death of my laptop
6431 <p
>But why is this happening? Why are my laptop batteries always
6432 dying in a year or two, while the batteries of space probes and
6433 satellites keep working year after year. If we are to believe
6434 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
6435 University
</a
>, the cause is me charging the battery whenever I have a
6436 chance, and the fix is to not charge the Lithium-ion batteries to
100%
6437 all the time, but to stay below
90% of full charge most of the time.
6438 I
've been told that the Tesla electric cars
6439 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
6440 the charge of their batteries to
80%
</a
>, with the option to charge to
6441 100% when preparing for a longer trip (not that I would want a car
6442 like Tesla where rights to privacy is abandoned, but that is another
6443 story), which I guess is the option we should have for laptops on
6444 Linux too.
</p
>
6446 <p
>Is there a good and generic way with Linux to tell the battery to
6447 stop charging at
80%, unless requested to charge to
100% once in
6448 preparation for a longer trip? I found
6449 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
6450 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
6451 80%
</a
>, but could not get it to work (kernel module refused to
6454 <p
>I wonder why the battery capacity was reported to be more than
100%
6455 at the start. I also wonder why the
"full capacity
" increases some
6456 times, and if it is possible to repeat the process to get the battery
6457 back to design capacity. And I wonder if the discharge and charge
6458 speed change over time, or if this stay the same. I did not yet try
6459 to write a tool to calculate the derivative values of the battery
6460 level, but suspect some interesting insights might be learned from
6463 <p
>Update
2015-
09-
24: I got a tip to install the packages
6464 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
6465 packages instead of the tp-smapi-dkms package I had tried to use
6466 initially, and use
'tlp setcharge
40 80' to change when charging start
6467 and stop. I
've done so now, but expect my existing battery is toast
6468 and need to be replaced. The proposal is unfortunately Thinkpad
6474 <title>New laptop - some more clues and ideas based on feedback
</title>
6475 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
6476 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
6477 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
6478 <description><p
>Several people contacted me after my previous blog post about my
6479 need for a new laptop, and provided very useful feedback. I wish to
6480 thank every one of these. Several pointed me to the possibility of
6481 fixing my X230, and I am already in the process of getting Lenovo to
6482 do so thanks to the on site, next day support contract covering the
6483 machine. But the battery is almost useless (I expect to replace it
6484 with a non-official battery) and I do not expect the machine to live
6485 for many more years, so it is time to plan its replacement. If I did
6486 not have a support contract, it was suggested to find replacement parts
6487 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
6488 might present a language barrier as I do not understand French.
</p
>
6490 <p
>One tip I got was to use the
6491 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
6492 compare laptop models. It seem to have more models available than
6493 prisjakt.no. Another tip I got from someone I know have similar
6494 keyboard preferences was that the HP EliteBook
840 keyboard is not
6495 very good, and this matches my experience with earlier EliteBook
6496 keyboards I tested. Because of this, I will not consider it any further.
6498 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
6499 newest Thinkpad X model. The keyboard reintroduces mouse buttons
6500 (which is missing from the X240), and is working fairly well with
6501 Debian Sid/Unstable according to
6502 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
6503 got on the keyboard quality are not consistent. Some say the keyboard
6504 is good, others say it is ok, while others say it is not very good.
6505 Those with experience from X41 and and X60 agree that the X250
6506 keyboard is not as good as those trusty old laptops, and suggest I
6507 keep and fix my X230 instead of upgrading, or get a used X230 to
6508 replace it. I
'm also told that the X250 lack leds for caps lock, disk
6509 activity and battery status, which is very convenient on my X230. I
'm
6510 also told that the CPU fan is running very often, making it a bit
6511 noisy. In any case, the X250 do not work out of the box with Debian
6512 Stable/Jessie, one of my requirements.
</p
>
6514 <p
>I have also gotten a few vendor proposals, one was
6515 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
6516 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
6517 The latter look very attractive to me.
</p
>
6519 <p
>Again, thank you all for the very useful feedback. It help a lot
6520 as I keep looking for a replacement.
</p
>
6522 <p
>Update
2015-
07-
06: I was recommended to check out the
6523 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
6525 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
6526 thinkpad X models
</a
>, and provide one year warranty.
</p
>
6531 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
6532 <link>https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</link>
6533 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</guid>
6534 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
6535 <description><p
>My primary work horse laptop is failing, and will need a
6536 replacement soon. The left
5 cm of the screen on my Thinkpad X230
6537 started flickering yesterday, and I suspect the cause is a broken
6538 cable, as changing the angle of the screen some times get rid of the
6539 flickering.
</p
>
6541 <p
>My requirements have not really changed since I bought it, and is
6543 <a href=
"https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
6544 described them in
2013</a
>. The last time I bought a laptop, I had
6546 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
6547 where I could select at least a few of the requirements (mouse pin,
6548 wifi, weight) and go through the rest manually. Three button mouse
6549 and a good keyboard is not available as an option, and all the three
6550 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
6551 G2) lack three mouse buttons). It is also unclear to me how good the
6552 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
6553 the keyboard, even if the quality and robustness in the X series have
6554 deteriorated since X41.
</p
>
6556 <p
>I wonder how I can find a sensible laptop when none of the options
6557 seem sensible to me? Are there better services around to search the
6558 set of available laptops for features? Please send me an email if you
6559 have suggestions.
</p
>
6561 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
6562 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
6563 of endorsed hardware
</a
>, which is useful background information.
</p
>
6568 <title>How to stay with sysvinit in Debian Jessie
</title>
6569 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
6570 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
6571 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
6572 <description><p
>By now, it is well known that Debian Jessie will not be using
6573 sysvinit as its boot system by default. But how can one keep using
6574 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
6576 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
6577 Schubert
</a
> and
6578 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
6581 <p
>If you already are using Wheezy and want to upgrade to Jessie and
6582 keep sysvinit as your boot system, create a file
6583 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
6584 you upgrade:
</p
>
6586 <p
><blockquote
><pre
>
6587 Package: systemd-sysv
6588 Pin: release o=Debian
6590 </pre
></blockquote
><p
>
6592 <p
>This file content will tell apt and aptitude to not consider
6593 installing systemd-sysv as part of any installation and upgrade
6594 solution when resolving dependencies, and thus tell it to avoid
6595 systemd as a default boot system. The end result should be that the
6596 upgraded system keep using sysvinit.
</p
>
6598 <p
>If you are installing Jessie for the first time, there is no way to
6599 get sysvinit installed by default (debootstrap used by
6600 debian-installer have no option for this), but one can tell the
6601 installer to switch to sysvinit before the first boot. Either by
6602 using a kernel argument to the installer, or by adding a line to the
6603 preseed file used. First, the kernel command line argument:
6605 <p
><blockquote
><pre
>
6606 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
6607 </pre
></blockquote
><p
>
6609 <p
>Next, the line to use in a preseed file:
</p
>
6611 <p
><blockquote
><pre
>
6612 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
6613 </pre
></blockquote
><p
>
6615 <p
>One can of course also do this after the first boot by installing
6616 the sysvinit-core package.
</p
>
6618 <p
>I recommend only using sysvinit if you really need it, as the
6619 sysvinit boot sequence in Debian have several hardware specific bugs
6620 on Linux caused by the fact that it is unpredictable when hardware
6621 devices show up during boot. But on the other hand, the new default
6622 boot system still have a few rough edges I hope will be fixed before
6623 Jessie is released.
</p
>
6625 <p
>Update
2014-
11-
26: Inspired by
6626 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
6627 blog post by Torsten Glaser
</a
>, added --purge to the preseed
6633 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
6634 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
6635 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
6636 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
6637 <description><p
>The right to communicate with your friends and family in private,
6638 without anyone snooping, is a right every citicen have in a liberal
6639 democracy. But this right is under serious attack these days.
</p
>
6641 <p
>A while back it occurred to me that one way to make the dragnet
6642 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
6643 the whisleblower Snowden) more expensive for Internet email,
6644 is to deliver all email using SMTP via Tor. Such SMTP option would be
6645 a nice addition to the FreedomBox project if we could send email
6646 between FreedomBox machines without leaking metadata about the emails
6647 to the people peeking on the wire. I
6648 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
6649 this on the FreedomBox project mailing list in October
</a
> and got a
6650 lot of useful feedback and suggestions. It also became obvious to me
6651 that this was not a novel idea, as the same idea was tested and
6652 documented by Johannes Berg as early as
2006, and both
6653 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
6654 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
6655 propose a similar method / protocol to pass emails between users.
</p
>
6657 <p
>To implement such system one need to set up a Tor hidden service
6658 providing the SMTP protocol on port
25, and use email addresses
6659 looking like username@hidden-service-name.onion. With such addresses
6660 the connections to port
25 on hidden-service-name.onion using Tor will
6661 go to the correct SMTP server. To do this, one need to configure the
6662 Tor daemon to provide the hidden service and the mail server to accept
6663 emails for this .onion domain. To learn more about Exim configuration
6664 in Debian and test the design provided by Johannes Berg in his FAQ, I
6665 set out yesterday to create a Debian package for making it trivial to
6666 set up such SMTP over Tor service based on Debian. Getting it to work
6667 were fairly easy, and
6668 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
6669 source code for the Debian package
</a
> is available from github. I
6670 plan to move it into Debian if further testing prove this to be a
6671 useful approach.
</p
>
6673 <p
>If you want to test this, set up a blank Debian machine without any
6674 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
6675 get rid of exim4). Install tor, clone the git repository mentioned
6676 above, build the deb and install it on the machine. Next, run
6677 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
6678 the instructions to get the service up and running. Restart tor and
6679 exim when it is done, and test mail delivery using swaks like
6682 <p
><blockquote
><pre
>
6683 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
6684 --to fbx@dutlqrrmjhtfa3vp.onion
6685 </pre
></blockquote
></p
>
6687 <p
>This will test the SMTP delivery using tor. Replace the email
6688 address with your own address to test your server. :)
</p
>
6690 <p
>The setup procedure is still to complex, and I hope it can be made
6691 easier and more automatic. Especially the tor setup need more work.
6692 Also, the package include a tor-smtp tool written in C, but its task
6693 should probably be rewritten in some script language to make the deb
6694 architecture independent. It would probably also make the code easier
6695 to review. The tor-smtp tool currently need to listen on a socket for
6696 exim to talk to it and is started using xinetd. It would be better if
6697 no daemon and no socket is needed. I suspect it is possible to get
6698 exim to run a command line tool for delivery instead of talking to a
6699 socket, and hope to figure out how in a future version of this
6702 <p
>Until I wipe my test machine, I can be reached using the
6703 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
6704 SMTorP. :)
</p
>
6709 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
6710 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
6711 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
6712 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
6713 <description><p
>If you ever had to moderate a mailman list, like the ones on
6714 alioth.debian.org, you know the web interface is fairly slow to
6715 operate. First you visit one web page, enter the moderation password
6716 and get a new page shown with a list of all the messages to moderate
6717 and various options for each email address. This take a while for
6718 every list you moderate, and you need to do it regularly to do a good
6719 job as a list moderator. But there is a quick alternative,
6720 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
6721 listadmin program
</a
>. It allow you to check lists for new messages
6722 to moderate in a fraction of a second. Here is a test run on two
6723 lists I recently took over:
</p
>
6725 <p
><blockquote
><pre
>
6726 % time listadmin xiph
6727 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
6728 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
6734 </pre
></blockquote
></p
>
6736 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
6737 there are no message in the moderation queue. Every morning I
6738 currently moderate
68 mailman lists, and it normally take around two
6739 minutes. When I took over the two pkg-xiph lists above a few days
6740 ago, there were
400 emails waiting in the moderator queue. It took me
6741 less than
15 minutes to process them all using the listadmin
6744 <p
>If you install
6745 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
6746 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
6747 with content like this, the moderation task is a breeze:
</p
>
6749 <p
><blockquote
><pre
>
6750 username username@example.org
6753 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
6756 adminurl https://{domain}/mailman/admindb/{list}
6757 mailman-list@lists.example.com
6760 other-list@otherserver.example.org
6761 </pre
></blockquote
></p
>
6763 <p
>There are other options to set as well. Check the manual page to
6764 learn the details.
</p
>
6766 <p
>If you are forced to moderate lists on a mailman installation where
6767 the SSL certificate is self signed or not properly signed by a
6768 generally accepted signing authority, you can set a environment
6769 variable when calling listadmin to disable SSL verification:
</p
>
6771 <p
><blockquote
><pre
>
6772 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
6773 </pre
></blockquote
></p
>
6775 <p
>If you want to moderate a subset of the lists you take care of, you
6776 can provide an argument to the listadmin script like I do in the
6777 initial screen dump (the xiph argument). Using an argument, only
6778 lists matching the argument string will be processed. This make it
6779 quick to accept messages if you notice the moderation request in your
6782 <p
>Without the listadmin program, I would never be the moderator of
68
6783 mailing lists, as I simply do not have time to spend on that if the
6784 process was any slower. The listadmin program have saved me hours of
6785 time I could spend elsewhere over the years. It truly is nice free
6788 <p
>As usual, if you use Bitcoin and want to show your support of my
6789 activities, please send Bitcoin donations to my address
6790 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6792 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
6793 configuration example. Also, I
've been told that the
6794 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
6800 <title>Debian Jessie, PXE and automatic firmware installation
</title>
6801 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
6802 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
6803 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
6804 <description><p
>When PXE installing laptops with Debian, I often run into the
6805 problem that the WiFi card require some firmware to work properly.
6806 And it has been a pain to fix this using preseeding in Debian.
6807 Normally something more is needed. But thanks to
6808 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
6809 package
</a
> and its recent tasksel extension, it has now become easy
6810 to do this using simple preseeding.
</p
>
6812 <p
>The isenkram-cli package provide tasksel tasks which will install
6813 firmware for the hardware found in the machine (actually, requested by
6814 the kernel modules for the hardware). (It can also install user space
6815 programs supporting the hardware detected, but that is not the focus
6816 of this story.)
</p
>
6818 <p
>To get this working in the default installation, two preeseding
6819 values are needed. First, the isenkram-cli package must be installed
6820 into the target chroot (aka the hard drive) before tasksel is executed
6821 in the pkgsel step of the debian-installer system. This is done by
6822 preseeding the base-installer/includes debconf value to include the
6823 isenkram-cli package. The package name is next passed to debootstrap
6824 for installation. With the isenkram-cli package in place, tasksel
6825 will automatically use the isenkram tasks to detect hardware specific
6826 packages for the machine being installed and install them, because
6827 isenkram-cli contain tasksel tasks.
</p
>
6829 <p
>Second, one need to enable the non-free APT repository, because
6830 most firmware unfortunately is non-free. This is done by preseeding
6831 the apt-mirror-setup step. This is unfortunate, but for a lot of
6832 hardware it is the only option in Debian.
</p
>
6834 <p
>The end result is two lines needed in your preseeding file to get
6835 firmware installed automatically by the installer:
</p
>
6837 <p
><blockquote
><pre
>
6838 base-installer base-installer/includes string isenkram-cli
6839 apt-mirror-setup apt-setup/non-free boolean true
6840 </pre
></blockquote
></p
>
6842 <p
>The current version of isenkram-cli in testing/jessie will install
6843 both firmware and user space packages when using this method. It also
6844 do not work well, so use version
0.15 or later. Installing both
6845 firmware and user space packages might give you a bit more than you
6846 want, so I decided to split the tasksel task in two, one for firmware
6847 and one for user space programs. The firmware task is enabled by
6848 default, while the one for user space programs is not. This split is
6849 implemented in the package currently in unstable.
</p
>
6851 <p
>If you decide to give this a go, please let me know (via email) how
6852 this recipe work for you. :)
</p
>
6854 <p
>So, I bet you are wondering, how can this work. First and
6855 foremost, it work because tasksel is modular, and driven by whatever
6856 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
6857 isenkram-cli package place two files for tasksel to find. First there
6858 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
6860 <p
><blockquote
><pre
>
6861 Task: isenkram-packages
6863 Description: Hardware specific packages (autodetected by isenkram)
6864 Based on the detected hardware various hardware specific packages are
6866 Test-new-install: show show
6868 Packages: for-current-hardware
6870 Task: isenkram-firmware
6872 Description: Hardware specific firmware packages (autodetected by isenkram)
6873 Based on the detected hardware various hardware specific firmware
6874 packages are proposed.
6875 Test-new-install: mark show
6877 Packages: for-current-hardware-firmware
6878 </pre
></blockquote
></p
>
6880 <p
>The key parts are Test-new-install which indicate how the task
6881 should be handled and the Packages line referencing to a script in
6882 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
6883 list of packages to install. The for-current-hardware-firmware script
6884 look like this to list relevant firmware for the machine:
6886 <p
><blockquote
><pre
>
6889 PATH=/usr/sbin:$PATH
6891 isenkram-autoinstall-firmware -l
6892 </pre
></blockquote
></p
>
6894 <p
>With those two pieces in place, the firmware is installed by
6895 tasksel during the normal d-i run. :)
</p
>
6897 <p
>If you want to test what tasksel will install when isenkram-cli is
6898 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
6899 --new-install
</tt
> to get the list of packages that tasksel would
6902 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
6903 pilots in testing this feature, as isenkram is used there now to
6904 install firmware, replacing the earlier scripts.
</p
>
6909 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
6910 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
6911 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
6912 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
6913 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
6914 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
6915 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
6916 on a screen normally showing the bread types and prizes:
</p
>
6918 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
6920 <p
>If it had booted as it was supposed to, I would never had known
6921 about this hidden Linux installation. It is interesting what
6922 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
6927 <title>New lsdvd release version
0.17 is ready
</title>
6928 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
6929 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
6930 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
6931 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
6932 got a new set of developers a few weeks ago, after the original
6933 developer decided to step down and pass the project to fresh blood.
6934 This project is now maintained by Petter Reinholdtsen and Steve
6937 <p
>I just wrapped up
6938 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
6939 new lsdvd release
</a
>, available in git or from
6940 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
6941 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
6946 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
6947 <li
>Check for garbage in the program chains, which indicate that a track is
6948 non-existant, to work around additional copy protection
</li
>
6949 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
6950 <li
>Fix pallete display of first entry
</li
>
6951 <li
>Fix include orders
</li
>
6952 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
6953 <li
>Fix the chapter count
</li
>
6954 <li
>Make sure the array size and the array limit used when initialising
6955 the palette size is the same.
</li
>
6956 <li
>Fix array printing.
</li
>
6957 <li
>Correct subsecond calculations.
</li
>
6958 <li
>Add sector information to the output format.
</li
>
6959 <li
>Clean up code to be closer to ANSI C and compile without warnings
6960 with more GCC compiler warnings.
</li
>
6964 <p
>This change bring together patches for lsdvd in use in various
6965 Linux and Unix distributions, as well as patches submitted to the
6966 project the last nine years. Please check it out. :)
</p
>
6971 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
6972 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
6973 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
6974 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
6975 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6976 project
</a
> provide a Linux solution for schools, including a
6977 powerful desktop with education software, a central server providing
6978 web pages, user database, user home directories, central login and PXE
6979 boot of both clients without disk and the installation to install Debian
6980 Edu on machines with disk (and a few other services perhaps to small
6981 to mention here). We in the Debian Edu team are currently working on
6982 the Jessie based version, trying to get everything in shape before the
6983 freeze, to avoid having to maintain our own package repository in the
6985 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
6986 status
</a
> can be seen on the Debian wiki, and there is still heaps of
6987 work left. Some fatal problems block testing, breaking the installer,
6988 but it is possible to work around these to get anyway. Here is a
6989 recipe on how to get the installation limping along.
</p
>
6991 <p
>First, download the test ISO via
6992 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
6993 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
6995 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
6996 The ISO build was broken on Tuesday, so we do not get a new ISO every
6997 12 hours or so, but thankfully the ISO we already got we are able to
6998 install with some tweaking.
</p
>
7000 <p
>When you get to the Debian Edu profile question, go to tty2
7001 (use Alt-Ctrl-F2), run
</p
>
7003 <p
><blockquote
><pre
>
7004 nano /usr/bin/edu-eatmydata-install
7005 </pre
></blockquote
></p
>
7007 <p
>and add
'exit
0' as the second line, disabling the eatmydata
7008 optimization. Return to the installation, select the profile you want
7009 and continue. Without this change, exim4-config will fail to install
7010 due to a known bug in eatmydata.
</p
>
7012 <p
>When you get the grub question at the end, answer /dev/sda (or if
7013 this do not work, figure out what your correct value would be. All my
7014 test machines need /dev/sda, so I have no advice if it do not fit
7015 your need.
</p
>
7017 <p
>If you installed a profile including a graphical desktop, log in as
7018 root after the initial boot from hard drive, and install the
7019 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
7020 or mate. If you want several desktop options, install more than one
7021 metapackage. Once this is done, reboot and you should have a working
7022 graphical login screen. This workaround should no longer be needed
7023 once the education-tasks package version
1.801 enter testing in two
7026 <p
>I believe the ISO build will start working on two days when the new
7027 tasksel package enter testing and Steve McIntyre get a chance to
7028 update the debian-cd git repository. The eatmydata, grub and desktop
7029 issues are already fixed in unstable and testing, and should show up
7030 on the ISO as soon as the ISO build start working again. Well the
7031 eatmydata optimization is really just disabled. The proper fix
7032 require an upload by the eatmydata maintainer applying the patch
7033 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
7034 The rest have proper fixes in unstable.
</p
>
7036 <p
>I hope this get you going with the installation testing, as we are
7037 quickly running out of time trying to get our Jessie based
7038 installation ready before the distribution freeze in a month.
</p
>
7043 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
7044 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
7045 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
7046 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
7047 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
7048 to handle my fairly large DVD collection. It is a nice command line
7049 tool to get details about a DVD, like title, tracks, track length,
7050 etc, in XML, Perl or human readable format. But lsdvd have not seen
7051 any new development since
2006 and had a few irritating bugs affecting
7052 its use with some DVDs. Upstream seemed to be dead, and in January I
7053 sent a small probe asking for a version control repository for the
7054 project, without any reply. But I use it regularly and would like to
7055 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
7056 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
7057 the project admin, and after getting a reply from him explaining that
7058 he was no longer interested in the project, I asked if I could take
7059 over. And yesterday, I became project admin.
</p
>
7061 <p
>I
've been in touch with a Gentoo developer and the Debian
7062 maintainer interested in joining forces to maintain the upstream
7063 project, and I hope we can get a new release out fairly quickly,
7064 collecting the patches spread around on the internet into on place.
7065 I
've added the relevant Debian patches to the freshly created git
7066 repository, and expect the Gentoo patches to make it too. If you got
7067 a DVD collection and care about command line tools, check out
7068 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
7069 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
7070 list
</a
>. :)
</p
>
7075 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
7076 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
7077 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
7078 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
7079 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
7080 a lot quicker. When we install more than
2000 packages in
7081 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
7082 tasksel in the installer, unpacking the binary packages take forever.
7083 A part of the slow I/O issue was discussed in
7084 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
7085 much file system sync-ing done by dpkg, which is the package
7086 responsible for unpacking the binary packages. Other parts (like code
7087 executed by postinst scripts) might also sync to disk during
7088 installation. All this sync-ing to disk do not really make sense to
7089 me. If the machine crash half-way through, I start over, I do not try
7090 to salvage the half installed system. So the failure sync-ing is
7091 supposed to protect against, hardware or system crash, is not really
7092 relevant while the installer is running.
</p
>
7094 <p
>A few days ago, I thought of a way to get rid of all the file
7095 system sync()-ing in a fairly non-intrusive way, without the need to
7096 change the code in several packages. The idea is not new, but I have
7097 not heard anyone propose the approach using dpkg-divert before. It
7098 depend on the small and clever package
7099 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
7100 uses LD_PRELOAD to replace the system functions for syncing data to
7101 disk with functions doing nothing, thus allowing programs to live
7102 dangerous while speeding up disk I/O significantly. Instead of
7103 modifying the implementation of dpkg, apt and tasksel (which are the
7104 packages responsible for selecting, fetching and installing packages),
7105 it occurred to me that we could just divert the programs away, replace
7106 them with a simple shell wrapper calling
7107 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
7108 Two days ago I decided to test the idea, and wrapped up a simple
7109 implementation for the Debian Edu udeb.
</p
>
7111 <p
>The effect was stunning. In my first test it reduced the running
7112 time of the pkgsel step (installing tasks) from
64 to less than
44
7113 minutes (
20 minutes shaved off the installation) on an old Dell
7114 Latitude D505 machine. I am not quite sure what the optimised time
7115 would have been, as I messed up the testing a bit, causing the debconf
7116 priority to get low enough for two questions to pop up during
7117 installation. As soon as I saw the questions I moved the installation
7118 along, but do not know how long the question were holding up the
7119 installation. I did some more measurements using Debian Edu Jessie,
7120 and got these results. The time measured is the time stamp in
7121 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
7122 "pkgsel: finishing up
" lines, if you want to do the same measurement
7123 yourself. In Debian Edu, the tasksel dialog do not show up, and the
7124 timing thus do not depend on how quickly the user handle the tasksel
7127 <p
><table
>
7130 <th
>Machine/setup
</th
>
7131 <th
>Original tasksel
</th
>
7132 <th
>Optimised tasksel
</th
>
7133 <th
>Reduction
</th
>
7137 <td
>Latitude D505 Main+LTSP LXDE
</td
>
7138 <td
>64 min (
07:
46-
08:
50)
</td
>
7139 <td
><44 min (
11:
27-
12:
11)
</td
>
7140 <td
>>20 min
18%
</td
>
7144 <td
>Latitude D505 Roaming LXDE
</td
>
7145 <td
>57 min (
08:
48-
09:
45)
</td
>
7146 <td
>34 min (
07:
43-
08:
17)
</td
>
7147 <td
>23 min
40%
</td
>
7151 <td
>Latitude D505 Minimal
</td
>
7152 <td
>22 min (
10:
37-
10:
59)
</td
>
7153 <td
>11 min (
11:
16-
11:
27)
</td
>
7154 <td
>11 min
50%
</td
>
7158 <td
>Thinkpad X200 Minimal
</td
>
7159 <td
>6 min (
08:
19-
08:
25)
</td
>
7160 <td
>4 min (
08:
04-
08:
08)
</td
>
7161 <td
>2 min
33%
</td
>
7165 <td
>Thinkpad X200 Roaming KDE
</td
>
7166 <td
>19 min (
09:
21-
09:
40)
</td
>
7167 <td
>15 min (
10:
25-
10:
40)
</td
>
7168 <td
>4 min
21%
</td
>
7171 </table
></p
>
7173 <p
>The test is done using a netinst ISO on a USB stick, so some of the
7174 time is spent downloading packages. The connection to the Internet
7175 was
100Mbit/s during testing, so downloading should not be a
7176 significant factor in the measurement. Download typically took a few
7177 seconds to a few minutes, depending on the amount of packages being
7178 installed.
</p
>
7180 <p
>The speedup is implemented by using two hooks in
7181 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
7182 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
7183 finish-install.d hook to remove the divert at the end of the
7184 installation. I picked the pre-pkgsel.d hook instead of the
7185 post-base-installer.d hook because I test using an ISO without the
7186 eatmydata package included, and the post-base-installer.d hook in
7187 Debian Edu can only operate on packages included in the ISO. The
7188 negative effect of this is that I am unable to activate this
7189 optimization for the kernel installation step in d-i. If the code is
7190 moved to the post-base-installer.d hook, the speedup would be larger
7191 for the entire installation.
</p
>
7193 <p
>I
've implemented this in the
7194 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
7195 git repository, and plan to provide the optimization as part of the
7196 Debian Edu installation. If you want to test this yourself, you can
7197 create two files in the installer (or in an udeb). One shell script
7198 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
7200 <p
><blockquote
><pre
>
7203 . /usr/share/debconf/confmodule
7205 logger -t my-pkgsel
"info: $*
"
7208 logger -t my-pkgsel
"error: $*
"
7210 override_install() {
7211 apt-install eatmydata || true
7212 if [ -x /target/usr/bin/eatmydata ] ; then
7213 for bin in dpkg apt-get aptitude tasksel ; do
7215 # Test that the file exist and have not been diverted already.
7216 if [ -f /target$file ] ; then
7217 info
"diverting $file using eatmydata
"
7218 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
7219 > /target$file.edu
7220 chmod
755 /target$file.edu
7221 in-target dpkg-divert --package debian-edu-config \
7222 --rename --quiet --add $file
7223 ln -sf ./$bin.edu /target$file
7225 error
"unable to divert $file, as it is missing.
"
7229 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
7234 </pre
></blockquote
></p
>
7236 <p
>To clean up, another shell script should go into
7237 /usr/lib/finish-install.d/ with code like this:
7239 <p
><blockquote
><pre
>
7241 . /usr/share/debconf/confmodule
7243 logger -t my-finish-install
"error: $@
"
7245 remove_install_override() {
7246 for bin in dpkg apt-get aptitude tasksel ; do
7248 if [ -x /target$file.edu ] ; then
7250 in-target dpkg-divert --package debian-edu-config \
7251 --rename --quiet --remove $file
7254 error
"Missing divert for $file.
"
7257 sync # Flush file buffers before continuing
7260 remove_install_override
7261 </pre
></blockquote
></p
>
7263 <p
>In Debian Edu, I placed both code fragments in a separate script
7264 edu-eatmydata-install and call it from the pre-pkgsel.d and
7265 finish-install.d scripts.
</p
>
7267 <p
>By now you might ask if this change should get into the normal
7268 Debian installer too? I suspect it should, but am not sure the
7269 current debian-installer coordinators find it useful enough. It also
7270 depend on the side effects of the change. I
'm not aware of any, but I
7271 guess we will see if the change is safe after some more testing.
7272 Perhaps there is some package in Debian depending on sync() and
7273 fsync() having effect? Perhaps it should go into its own udeb, to
7274 allow those of us wanting to enable it to do so without affecting
7277 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
7278 will break installation of all programs using gnutls because of
7279 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
7280 eatmydata package in Debian will solve it.
</p
>
7282 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
7283 the optimization work again. And I have discovered that the
7284 dpkg-divert trick is not really needed and implemented a slightly
7285 simpler approach as part of the debian-edu-install package. See
7286 tools/edu-eatmydata-install in the source package.
</p
>
7288 <p
>Update
2014-
11-
11: Unfortunately, a new
7289 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
7290 triggering on i386 made it into testing, and broke this installation
7291 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
7292 request
768893</a
> is accepted, it should be working again.
</p
>
7297 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
7298 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
7299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
7300 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
7301 <description><p
>Yesterday, I had the pleasure of attending a talk with the
7302 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
7303 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
7304 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
7305 learn that there is a large set of publicly available key servers to
7306 use when looking for peoples public key. So far I have used
7307 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
7308 were misbehaving, but those days are ended. The servers I have used
7309 up until yesterday have been slow and some times unavailable. I hope
7310 those problems are gone now.
</p
>
7312 <p
>Behind the round robin DNS entry of the
7313 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
7314 there is a pool of more than
100 keyservers which are checked every
7315 day to ensure they are well connected and up to date. It must be
7316 better than what I have used so far. :)
</p
>
7318 <p
>Yesterdays speaker told me that the service is the default
7319 keyserver provided by the default configuration in GnuPG, but this do
7320 not seem to be used in Debian. Perhaps it should?
</p
>
7322 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
7325 <p
><blockquote
><pre
>
7326 keyserver pool.sks-keyservers.net
7327 </pre
></blockquote
></p
>
7329 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
7330 entries in DNS. Just for fun, I did just that at work, so now every
7331 user of GnuPG at the University of Oslo should find a OpenGPG
7332 keyserver automatically should their need it:
</p
>
7334 <p
><blockquote
><pre
>
7335 % host -t srv _pgpkey-http._tcp.uio.no
7336 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
7338 </pre
></blockquote
></p
>
7340 <p
>Now if only
7341 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
7342 HKP lookup protocol
</a
> supported finding signature paths, I would be
7343 very happy. It can look up a given key or search for a user ID, but I
7344 normally do not want that, but to find a trust path from my key to
7345 another key. Given a user ID or key ID, I would like to find (and
7346 download) the keys representing a signature path from my key to the
7347 key in question, to be able to get a trust path between the two keys.
7348 This is as far as I can tell not possible today. Perhaps something
7349 for a future version of the protocol?
</p
>
7354 <title>From English wiki to translated PDF and epub via Docbook
</title>
7355 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
7356 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
7357 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
7358 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
7359 project
</a
> provide an instruction manual for teachers, system
7360 administrators and other users that contain useful tips for setting up
7361 and maintaining a Debian Edu installation. This text is about how the
7362 text processing of this manual is handled in the project.
</p
>
7364 <p
>One goal of the project is to provide information in the native
7365 language of its users, and for this we need to handle translations.
7366 But we also want to make sure each language contain the same
7367 information, so for this we need a good way to keep the translations
7368 in sync. And we want it to be easy for our users to improve the
7369 documentation, avoiding the need to learn special formats or tools to
7370 contribute, and the obvious way to do this is to make it possible to
7371 edit the documentation using a web browser. We also want it to be
7372 easy for translators to keep the translation up to date, and give them
7373 help in figuring out what need to be translated. Here is the list of
7374 tools and the process we have found trying to reach all these
7377 <p
>We maintain the authoritative source of our manual in the
7378 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
7379 wiki
</a
>, as several wiki pages written in English. It consist of one
7380 front page with references to the different chapters, several pages
7381 for each chapter, and finally one
"collection page
" gluing all the
7382 chapters together into one large web page (aka
7383 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
7384 AllInOne page
</a
>). The AllInOne page is the one used for further
7385 processing and translations. Thanks to the fact that the
7386 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
7387 wiki.debian.org support exporting pages in
7388 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
7389 the list of pages to export using the raw version of the AllInOne
7390 page, loop over each of them to generate a Docbook XML version of the
7391 manual. This process also download images and transform image
7392 references to use the locally downloaded images. The generated
7393 Docbook XML files are slightly broken, so some post-processing is done
7394 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
7395 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
7396 a handfull of images. The XML file can now be used to generate PDF, HTML
7397 and epub versions of the English manual. This is the basic step of
7398 our process, making PDF (using dblatex), HTML (using xsltproc) and
7399 epub (using dbtoepub) version from Docbook XML, and the resulting files
7400 are placed in the debian-edu-doc-en binary package.
</p
>
7402 <p
>But English documentation is not enough for us. We want translated
7403 documentation too, and we want to make it easy for translators to
7404 track the English original. For this we use the
7405 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
7406 which allow us to transform the English Docbook XML file into a
7407 translation file (a .pot file), usable with the normal gettext based
7408 translation tools used by those translating free software. The pot
7409 file is used to create and maintain translation files (several .po
7410 files), which the translations update with the native language
7411 translations of all titles, paragraphs and blocks of text in the
7412 original. The next step is combining the original English Docbook XML
7413 and the translation file (say debian-edu-wheezy-manual.nb.po), to
7414 create a translated Docbook XML file (in this case
7415 debian-edu-wheezy-manual.nb.xml). This translated (or partly
7416 translated, if the translation is not complete) Docbook XML file can
7417 then be used like the original to create a PDF, HTML and epub version
7418 of the documentation.
</p
>
7420 <p
>The translators use different tools to edit the .po files. We
7422 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
7423 while some use emacs and vi, others can use web based editors like
7424 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
7425 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
7426 is where the .po file end up, in our git repository. Updated
7427 translations can either be committed directly to git, or submitted as
7428 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
7429 against the debian-edu-doc package
</a
>.
</p
>
7431 <p
>One challenge is images, which both might need to be translated (if
7432 they show translated user applications), and are needed in different
7433 formats when creating PDF and HTML versions (epub is a HTML version in
7434 this regard). For this we transform the original PNG images to the
7435 needed density and format during build, and have a way to provide
7436 translated images by storing translated versions in
7437 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
7438 package maintainers know more.
</p
>
7440 <p
>If you wonder what the result look like, we provide
7441 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
7442 of the documentation packages on the web
</a
>. See for example the
7443 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
7444 PDF version
</a
> or the
7445 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
7446 HTML version
</a
>. We do not yet build the epub version by default,
7447 but perhaps it will be done in the future.
</p
>
7449 <p
>To learn more, check out
7450 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
7451 debian-edu-doc package
</a
>,
7452 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
7453 manual on the wiki
</a
> and
7454 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
7455 translation instructions
</a
> in the manual.
</p
>
7460 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
7461 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
7462 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
7463 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
7464 <description><p
>It would be nice if it was easier in Debian to get all the hardware
7465 related packages relevant for the computer installed automatically.
7466 So I implemented one, using
7467 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
7468 package
</a
>. To use it, install the tasksel and isenkram packages and
7469 run tasksel as user root. You should be presented with a new option,
7470 "Hardware specific packages (autodetected by isenkram)
". When you
7471 select it, tasksel will install the packages isenkram claim is fit for
7472 the current hardware, hot pluggable or not.
<p
>
7474 <p
>The implementation is in two files, one is the tasksel menu entry
7475 description, and the other is the script used to extract the list of
7476 packages to install. The first part is in
7477 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
7480 <p
><blockquote
><pre
>
7483 Description: Hardware specific packages (autodetected by isenkram)
7484 Based on the detected hardware various hardware specific packages are
7486 Test-new-install: mark show
7488 Packages: for-current-hardware
7489 </pre
></blockquote
></p
>
7491 <p
>The second part is in
7492 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
7495 <p
><blockquote
><pre
>
7500 isenkram-autoinstall-firmware -l
7502 </pre
></blockquote
></p
>
7504 <p
>All in all, a very short and simple implementation making it
7505 trivial to install the hardware dependent package we all may want to
7506 have installed on our machines. I
've not been able to find a way to
7507 get tasksel to tell you exactly which packages it plan to install
7508 before doing the installation. So if you are curious or careful,
7509 check the output from the isenkram-* command line tools first.
</p
>
7511 <p
>The information about which packages are handling which hardware is
7512 fetched either from the isenkram package itself in
7513 /usr/share/isenkram/, from git.debian.org or from the APT package
7514 database (using the Modaliases header). The APT package database
7515 parsing have caused a nasty resource leak in the isenkram daemon (bugs
7516 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
7517 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
7518 the python-apt code (bug
7519 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
7520 workaround I was able to get rid of the file descriptor leak and
7521 reduce the memory leak from ~
30 MiB per hardware detection down to
7522 around
2 MiB per hardware detection. It should make the desktop
7523 daemon a lot more useful. The fix is in version
0.7 uploaded to
7524 unstable today.
</p
>
7526 <p
>I believe the current way of mapping hardware to packages in
7527 Isenkram is is a good draft, but in the future I expect isenkram to
7528 use the AppStream data source for this. A proposal for getting proper
7529 AppStream support into Debian is floating around as
7530 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
7531 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
7532 project
</a
> will take place this summer to improve the situation. I
7533 look forward to seeing the result, and welcome patches for isenkram to
7534 start using the information when it is ready.
</p
>
7536 <p
>If you want your package to map to some specific hardware, either
7537 add a
"Xb-Modaliases
" header to your control file like I did in
7538 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
7539 package
</a
> or submit a bug report with the details to the isenkram
7541 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
7542 blog posts tagged isenkram
</a
> for details on the notation. I expect
7543 the information will be migrated to AppStream eventually, but for the
7544 moment I got no better place to store it.
</p
>
7549 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
7550 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
7551 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
7552 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
7553 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
7554 project
</a
> is working on providing the software and hardware to make
7555 it easy for non-technical people to host their data and communication
7556 at home, and being able to communicate with their friends and family
7557 encrypted and away from prying eyes. It is still going strong, and
7558 today a major mile stone was reached.
</p
>
7560 <p
>Today, the last of the packages currently used by the project to
7561 created the system images were accepted into Debian Unstable. It was
7562 the freedombox-setup package, which is used to configure the images
7563 during build and on the first boot. Now all one need to get going is
7564 the build code from the freedom-maker git repository and packages from
7565 Debian. And once the freedombox-setup package enter testing, we can
7566 build everything directly from Debian. :)
</p
>
7568 <p
>Some key packages used by Freedombox are
7569 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
7570 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
7571 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
7572 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
7573 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
7574 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
7575 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
7576 are plans to integrate more packages into the setup. User
7577 documentation is maintained on the Debian wiki. Please
7578 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
7579 the manual
</a
> and help us improve it.
</p
>
7581 <p
>To test for yourself and create boot images with the FreedomBox
7582 setup, run this on a Debian machine using a user with sudo rights to
7583 become root:
</p
>
7585 <p
><pre
>
7586 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7587 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7589 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7591 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7592 </pre
></p
>
7594 <p
>Root access is needed to run debootstrap and mount loopback
7595 devices. See the README in the freedom-maker git repo for more
7596 details on the build. If you do not want all three images, trim the
7597 make line. Note that the virtualbox-image target is not really
7598 virtualbox specific. It create a x86 image usable in kvm, qemu,
7599 vmware and any other x86 virtual machine environment. You might need
7600 the version of vmdebootstrap in Jessie to get the build working, as it
7601 include fixes for a race condition with kpartx.
</p
>
7603 <p
>If you instead want to install using a Debian CD and the preseed
7604 method, boot a Debian Wheezy ISO and use this boot argument to load
7605 the preseed values:
</p
>
7607 <p
><pre
>
7608 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
7609 </pre
></p
>
7611 <p
>I have not tested it myself the last few weeks, so I do not know if
7612 it still work.
</p
>
7614 <p
>If you wonder how to help, one task you could look at is using
7615 systemd as the boot system. It will become the default for Linux in
7616 Jessie, so we need to make sure it is usable on the Freedombox. I did
7617 a simple test a few weeks ago, and noticed dnsmasq failed to start
7618 during boot when using systemd. I suspect there are other problems
7619 too. :) To detect problems, there is a test suite included, which can
7620 be run from the plinth web interface.
</p
>
7622 <p
>Give it a go and let us know how it goes on the mailing list, and help
7623 us get the new release published. :) Please join us on
7624 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
7625 irc.debian.org)
</a
> and
7626 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7627 mailing list
</a
> if you want to help make this vision come true.
</p
>
7632 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
7633 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
7634 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
7635 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
7636 <description><p
>For a while now, I have been looking for a sensible offsite backup
7637 solution for use at home. My requirements are simple, it must be
7638 cheap and locally encrypted (in other words, I keep the encryption
7639 keys, the storage provider do not have access to my private files).
7640 One idea me and my friends had many years ago, before the cloud
7641 storage providers showed up, was to use Google mail as storage,
7642 writing a Linux block device storing blocks as emails in the mail
7643 service provided by Google, and thus get heaps of free space. On top
7644 of this one can add encryption, RAID and volume management to have
7645 lots of (fairly slow, I admit that) cheap and encrypted storage. But
7646 I never found time to implement such system. But the last few weeks I
7647 have looked at a system called
7648 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
7649 mounted network backed file system with the features I need.
</p
>
7651 <p
>S3QL is a fuse file system with a local cache and cloud storage,
7652 handling several different storage providers, any with Amazon S3,
7653 Google Drive or OpenStack API. There are heaps of such storage
7654 providers. S3QL can also use a local directory as storage, which
7655 combined with sshfs allow for file storage on any ssh server. S3QL
7656 include support for encryption, compression, de-duplication, snapshots
7657 and immutable file systems, allowing me to mount the remote storage as
7658 a local mount point, look at and use the files as if they were local,
7659 while the content is stored in the cloud as well. This allow me to
7660 have a backup that should survive fire. The file system can not be
7661 shared between several machines at the same time, as only one can
7662 mount it at the time, but any machine with the encryption key and
7663 access to the storage service can mount it if it is unmounted.
</p
>
7665 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
7666 package is included already. So to get started, run
<tt
>apt-get
7667 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
7668 Greenqloud, after reading their nice recipe on
7669 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
7670 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
7671 in Iceland more than those in USA when it come to keeping my personal
7672 data safe and private, and thus would rather spend money on a company
7673 in Iceland. Another nice recipe is available from the article
7674 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
7675 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
7676 Admin magazine. When the provider is picked, figure out how to get
7677 the API key needed to connect to the storage API. With Greencloud,
7678 the key did not show up until I had added payment details to my
7681 <p
>Armed with the API access details, it is time to create the file
7682 system. First, create a new bucket in the cloud. This bucket is the
7683 file system storage area. I picked a bucket name reflecting the
7684 machine that was going to store data there, but any name will do.
7685 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
7686 the API login and password, and a locally created password. Store it
7687 all in ~root/.s3ql/authinfo2 like this:
7689 <p
><blockquote
><pre
>
7691 storage-url: s3c://s.greenqloud.com:
443/bucket-name
7692 backend-login: API-login
7693 backend-password: API-password
7694 fs-passphrase: local-password
7695 </pre
></blockquote
></p
>
7697 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
7698 but any sensible way to create a fairly random password should do it.
7699 Armed with these details, it is now time to run mkfs, entering the API
7700 details and password to create it:
</p
>
7702 <p
><blockquote
><pre
>
7703 # mkdir -m
700 /var/lib/s3ql-cache
7704 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7705 --ssl s3c://s.greenqloud.com:
443/bucket-name
7706 Enter backend login:
7707 Enter backend password:
7708 Before using S3QL, make sure to read the user
's guide, especially
7709 the
'Important Rules to Avoid Loosing Data
' section.
7710 Enter encryption password:
7711 Confirm encryption password:
7712 Generating random encryption key...
7713 Creating metadata tables...
7723 Compressing and uploading metadata...
7724 Wrote
0.00 MB of compressed metadata.
7725 #
</pre
></blockquote
></p
>
7727 <p
>The next step is mounting the file system to make the storage available.
7729 <p
><blockquote
><pre
>
7730 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7731 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
7732 Using
4 upload threads.
7733 Downloading and decompressing metadata...
7743 Mounting filesystem...
7745 Filesystem Size Used Avail Use% Mounted on
7746 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
7748 </pre
></blockquote
></p
>
7750 <p
>The file system is now ready for use. I use rsync to store my
7751 backups in it, and as the metadata used by rsync is downloaded at
7752 mount time, no network traffic (and storage cost) is triggered by
7753 running rsync. To unmount, one should not use the normal umount
7754 command, as this will not flush the cache to the cloud storage, but
7755 instead running the umount.s3ql command like this:
7757 <p
><blockquote
><pre
>
7760 </pre
></blockquote
></p
>
7762 <p
>There is a fsck command available to check the file system and
7763 correct any problems detected. This can be used if the local server
7764 crashes while the file system is mounted, to reset the
"already
7765 mounted
" flag. This is what it look like when processing a working
7766 file system:
</p
>
7768 <p
><blockquote
><pre
>
7769 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
7770 Using cached metadata.
7771 File system seems clean, checking anyway.
7772 Checking DB integrity...
7773 Creating temporary extra indices...
7774 Checking lost+found...
7775 Checking cached objects...
7776 Checking names (refcounts)...
7777 Checking contents (names)...
7778 Checking contents (inodes)...
7779 Checking contents (parent inodes)...
7780 Checking objects (reference counts)...
7781 Checking objects (backend)...
7782 ..processed
5000 objects so far..
7783 ..processed
10000 objects so far..
7784 ..processed
15000 objects so far..
7785 Checking objects (sizes)...
7786 Checking blocks (referenced objects)...
7787 Checking blocks (refcounts)...
7788 Checking inode-block mapping (blocks)...
7789 Checking inode-block mapping (inodes)...
7790 Checking inodes (refcounts)...
7791 Checking inodes (sizes)...
7792 Checking extended attributes (names)...
7793 Checking extended attributes (inodes)...
7794 Checking symlinks (inodes)...
7795 Checking directory reachability...
7796 Checking unix conventions...
7797 Checking referential integrity...
7798 Dropping temporary indices...
7799 Backing up old metadata...
7809 Compressing and uploading metadata...
7810 Wrote
0.89 MB of compressed metadata.
7812 </pre
></blockquote
></p
>
7814 <p
>Thanks to the cache, working on files that fit in the cache is very
7815 quick, about the same speed as local file access. Uploading large
7816 amount of data is to me limited by the bandwidth out of and into my
7817 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
7818 which is very close to my upload speed, and downloading the same
7819 Debian installation ISO gave me
610 kiB/s, close to my download speed.
7820 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
7821 network, not the file system code. I do not know what a good cache
7822 size would be, but suspect that the cache should e larger than your
7823 working set.
</p
>
7825 <p
>I mentioned that only one machine can mount the file system at the
7826 time. If another machine try, it is told that the file system is
7829 <p
><blockquote
><pre
>
7830 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7831 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
7832 Using
8 upload threads.
7833 Backend reports that fs is still mounted elsewhere, aborting.
7835 </pre
></blockquote
></p
>
7837 <p
>The file content is uploaded when the cache is full, while the
7838 metadata is uploaded once every
24 hour by default. To ensure the
7839 file system content is flushed to the cloud, one can either umount the
7840 file system, or ask S3QL to flush the cache and metadata using
7843 <p
><blockquote
><pre
>
7844 # s3qlctrl upload-meta /s3ql
7845 # s3qlctrl flushcache /s3ql
7847 </pre
></blockquote
></p
>
7849 <p
>If you are curious about how much space your data uses in the
7850 cloud, and how much compression and deduplication cut down on the
7851 storage usage, you can use s3qlstat on the mounted file system to get
7854 <p
><blockquote
><pre
>
7856 Directory entries:
9141
7859 Total data size:
22049.38 MB
7860 After de-duplication:
21955.46 MB (
99.57% of total)
7861 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
7862 Database size:
2.39 MB (uncompressed)
7863 (some values do not take into account not-yet-uploaded dirty blocks in cache)
7865 </pre
></blockquote
></p
>
7867 <p
>I mentioned earlier that there are several possible suppliers of
7868 storage. I did not try to locate them all, but am aware of at least
7869 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
7870 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
7871 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
7872 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
7873 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
7874 accept payment in Bitcoin. Pick one that suit your need. Some of
7875 them provide several GiB of free storage, but the prize models are
7876 quite different and you will have to figure out what suits you
7879 <p
>While researching this blog post, I had a look at research papers
7880 and posters discussing the S3QL file system. There are several, which
7881 told me that the file system is getting a critical check by the
7882 science community and increased my confidence in using it. One nice
7884 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
7885 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
7886 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
7887 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
7888 and Pamela Smith. Please have a look.
</p
>
7890 <p
>Given my problems with different file systems earlier, I decided to
7891 check out the mounted S3QL file system to see if it would be usable as
7892 a home directory (in other word, that it provided POSIX semantics when
7893 it come to locking and umask handling etc). Running
7894 <a href=
"https://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
7895 test code to check file system semantics
</a
>, I was happy to discover that
7896 no error was found. So the file system can be used for home
7897 directories, if one chooses to do so.
</p
>
7899 <p
>If you do not want a locally file system, and want something that
7900 work without the Linux fuse file system, I would like to mention the
7901 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
7902 provide locally encrypted backup using a command line client. It have
7903 a nicer access control system, where one can split out read and write
7904 access, allowing some systems to write to the backup and others to
7905 only read from it.
</p
>
7907 <p
>As usual, if you use Bitcoin and want to show your support of my
7908 activities, please send Bitcoin donations to my address
7909 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7914 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
7915 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
7916 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
7917 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
7918 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
7919 project
</a
> is working on providing the software and hardware for
7920 making it easy for non-technical people to host their data and
7921 communication at home, and being able to communicate with their
7922 friends and family encrypted and away from prying eyes. It has been
7923 going on for a while, and is slowly progressing towards a new test
7924 release (
0.2).
</p
>
7926 <p
>And what day could be better than the Pi day to announce that the
7927 new version will provide
"hard drive
" / SD card / USB stick images for
7928 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
7929 system), and can also be installed using a Debian installer preseed
7930 file. The Debian based Freedombox is now based on Debian Jessie,
7931 where most of the needed packages used are already present. Only one,
7932 the freedombox-setup package, is missing. To try to build your own
7933 boot image to test the current status, fetch the freedom-maker scripts
7935 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
7936 with a user with sudo access to become root:
7939 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7941 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7942 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7944 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7947 <p
>Root access is needed to run debootstrap and mount loopback
7948 devices. See the README for more details on the build. If you do not
7949 want all three images, trim the make line. But note that thanks to
<a
7950 href=
"https://bugs.debian.org/
741407">a race condition in
7951 vmdebootstrap
</a
>, the build might fail without the patch to the
7952 kpartx call.
</p
>
7954 <p
>If you instead want to install using a Debian CD and the preseed
7955 method, boot a Debian Wheezy ISO and use this boot argument to load
7956 the preseed values:
</p
>
7959 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
7962 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
7963 recently introduced bug in apt in Jessie
</a
>, the installer will
7964 currently hang while setting up APT sources. Killing the
7965 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
7966 installation will get the installation going. This affect all
7967 installations in Jessie, and I expect it will be fixed soon.
</p
>
7969 <p
>Give it a go and let us know how it goes on the mailing list, and help
7970 us get the new release published. :) Please join us on
7971 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
7972 irc.debian.org)
</a
> and
7973 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7974 mailing list
</a
> if you want to help make this vision come true.
</p
>
7979 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
7980 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
7981 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
7982 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
7983 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
7984 innetgr tools, because I needed them in
7985 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
7986 ng-utils, and it has served me well. I placed the project under the
7987 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
7988 repository. But many years ago, the CVS repository was dropped (lost,
7989 not migrated to new hardware, not sure), and the project have lacked a
7990 proper home since then.
</p
>
7992 <p
>Last summer, I had a look at the package and made a new release
7993 fixing a irritating crash bug, but was unable to store the changes in
7994 a proper source control system. I applied for a project on
7995 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
7996 to follow up on it. Until today. :)
</p
>
7998 <p
>After many hours of cleaning and migration, the ng-utils project
7999 now have a new home, and a git repository with the highlight of the
8000 history of the project. I published all release tarballs and imported
8001 them into the git repository. As the project is really stable and not
8002 expected to gain new features any time soon, I decided to make a new
8003 release and call it
1.0. Visit the new project home on
8004 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
8005 if you want to check it out. The new version is also uploaded into
8006 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
8011 <title>Testing sysvinit from experimental in Debian Hurd
</title>
8012 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
8013 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
8014 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
8015 <description><p
>A few days ago I decided to try to help the Hurd people to get
8016 their changes into sysvinit, to allow them to use the normal sysvinit
8017 boot system instead of their old one. This follow up on the
8018 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
8019 Google Summer of Code work
</a
> done last summer by Justus Winter to
8020 get Debian on Hurd working more like Debian on Linux. To get started,
8021 I downloaded a prebuilt hard disk image from
8022 <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
>,
8023 and started it using virt-manager.
</p
>
8025 <p
>The first think I had to do after logging in (root without any
8026 password) was to get the network operational. I followed
8027 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
8028 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
8029 commands as root to get the machine to accept a IP address from the
8030 kvm internal DHCP server:
</p
>
8032 <p
><blockquote
><pre
>
8033 settrans -fgap /dev/netdde /hurd/netdde
8034 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
8035 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
8037 </pre
></blockquote
></p
>
8039 <p
>After this, the machine had internet connectivity, and I could
8040 upgrade it and install the sysvinit packages from experimental and
8041 enable it as the default boot system in Hurd.
</p
>
8043 <p
>But before I did that, I set a password on the root user, as ssh is
8044 running on the machine it for ssh login to work a password need to be
8045 set. Also, note that a bug somewhere in openssh on Hurd block
8046 compression from working. Remember to turn that off on the client
8049 <p
>Run these commands as root to upgrade and test the new sysvinit
8052 <p
><blockquote
><pre
>
8053 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
8054 deb http://http.debian.net/debian/ experimental main
8057 apt-get dist-upgrade
8058 apt-get install -t experimental initscripts sysv-rc sysvinit \
8059 sysvinit-core sysvinit-utils
8060 update-alternatives --config runsystem
8061 </pre
></blockquote
></p
>
8063 <p
>To reboot after switching boot system, you have to use
8064 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
8065 yet a sysvinit process able to receive the signals from the normal
8066 'reboot
' command. After switching to sysvinit as the boot system,
8067 upgrading every package and rebooting, the network come up with DHCP
8068 after boot as it should, and the settrans/pkill hack mentioned at the
8069 start is no longer needed. But for some strange reason, there are no
8070 longer any login prompt in the virtual console, so I logged in using
8073 <p
>Note that there are some race conditions in Hurd making the boot
8074 fail some times. No idea what the cause is, but hope the Hurd porters
8075 figure it out. At least Justus said on IRC (#debian-hurd on
8076 irc.debian.org) that they are aware of the problem. A way to reduce
8077 the impact is to upgrade to the Hurd packages built by Justus by
8078 adding this repository to the machine:
</p
>
8080 <p
><blockquote
><pre
>
8081 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
8082 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
8084 </pre
></blockquote
></p
>
8086 <p
>At the moment the prebuilt virtual machine get some packages from
8087 http://ftp.debian-ports.org/debian, because some of the packages in
8088 unstable do not yet include the required patches that are lingering in
8089 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
8091 <p
><blockquote
><pre
>
8092 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
8093 i emacs - GNU Emacs editor (metapackage)
8094 i gdb - GNU Debugger
8095 i hurd-recommended - Miscellaneous translators
8096 i isc-dhcp-client - ISC DHCP client
8097 i isc-dhcp-common - common files used by all the isc-dhcp* packages
8098 i libc-bin - Embedded GNU C Library: Binaries
8099 i libc-dev-bin - Embedded GNU C Library: Development binaries
8100 i libc0.3 - Embedded GNU C Library: Shared libraries
8101 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
8102 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
8103 i multiarch-support - Transitional package to ensure multiarch compatibilit
8104 i A x11-common - X Window System (X.Org) infrastructure
8105 i xorg - X.Org X Window System
8106 i A xserver-xorg - X.Org X server
8107 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
8109 </pre
></blockquote
></p
>
8111 <p
>All in all, testing hurd has been an interesting experience. :)
8112 X.org did not work out of the box and I never took the time to follow
8113 the porters instructions to fix it. This time I was interested in the
8114 command line stuff.
<p
>
8119 <title>New chrpath release
0.16</title>
8120 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
8121 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
8122 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
8123 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
8124 find problems in C, C++ and Java code using static source code
8125 analysis. It can detect a lot of different problems, and is very
8126 useful to find memory and locking bugs in the error handling part of
8127 the source. The company behind it provide
8128 <a href=
"https://scan.coverity.com/
">check of free software projects as
8129 a community service
</a
>, and many hundred free software projects are
8130 already checked. A few days ago I decided to have a closer look at
8131 the Coverity system, and discovered that the
8132 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
8133 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
8134 projects I am involved with was already registered. But these are
8135 fairly big, and I would also like to have a small and easy project to
8136 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
8137 checking of the chrpath project
</a
>. It was
8138 added to the checker and discovered seven potential defects. Six of
8139 these were real, mostly resource
"leak
" when the program detected an
8140 error. Nothing serious, as the resources would be released a fraction
8141 of a second later when the program exited because of the error, but it
8142 is nice to do it right in case the source of the program some time in
8143 the future end up in a library. Having fixed all defects and added
8144 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
8145 mailing list for the chrpath developers
</a
>, I decided it was time to
8146 publish a new release. These are the release notes:
</p
>
8148 <p
>New in
0.16 released
2014-
01-
14:
</p
>
8152 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
8153 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
8154 <li
>Mention new project mailing list in the documentation.
</li
>
8159 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
8160 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
8161 project if something is wrong with the new release. The test suite
8162 did not discover any old errors, so if you find a new one, please also
8163 include a test suite check.
</p
>
8168 <title>New chrpath release
0.15</title>
8169 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
8170 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
8171 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
8172 <description><p
>After many years break from the package and a vain hope that
8173 development would be continued by someone else, I finally pulled my
8174 acts together this morning and wrapped up a new release of chrpath,
8175 the command line tool to modify the rpath and runpath of already
8176 compiled ELF programs. The update was triggered by the persistence of
8177 Isha Vishnoi at IBM, which needed a new config.guess file to get
8178 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
8179 is working on. I checked the
8180 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
8181 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
8182 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
8183 packages for interesting patches (failed to find the source from
8184 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
8185 These are the release notes:
</p
>
8187 <p
>New in
0.15 released
2013-
11-
24:
</p
>
8191 <li
>Updated config.sub and config.guess from the GNU project to work
8192 with newer architectures. Thanks to isha vishnoi for the heads
8195 <li
>Updated README with current URLs.
</li
>
8197 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
8198 Matthias Klose.
</li
>
8200 <li
>Added missing help for -k|--keepgoing option, using patch by
8201 Petr Machata found in Fedora.
</li
>
8203 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
8204 .dynamic is a NULL terminated string. Based on patch found in
8205 Fedora credited Axel Thimm and Christian Krause.
</li
>
8210 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
8211 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
8212 project if something is wrong with the new release. The test suite
8213 did not discover any old errors, so if you find a new one, please also
8214 include a testsuite check.
</p
>
8219 <title>Debian init.d boot script example for rsyslog
</title>
8220 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
8221 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
8222 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
8223 <description><p
>If one of the points of switching to a new init system in Debian is
8224 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
8225 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
8226 init.d scripts at all. Here is an example init.d script, ie a rewrite
8227 of /etc/init.d/rsyslog:
</p
>
8229 <p
><pre
>
8230 #!/lib/init/init-d-script
8233 # Required-Start: $remote_fs $time
8234 # Required-Stop: umountnfs $time
8235 # X-Stop-After: sendsigs
8236 # Default-Start:
2 3 4 5
8237 # Default-Stop:
0 1 6
8238 # Short-Description: enhanced syslogd
8239 # Description: Rsyslog is an enhanced multi-threaded syslogd.
8240 # It is quite compatible to stock sysklogd and can be
8241 # used as a drop-in replacement.
8243 DESC=
"enhanced syslogd
"
8244 DAEMON=/usr/sbin/rsyslogd
8245 </pre
></p
>
8247 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
8248 script was
137 lines, and the above is just
15 lines, most of it meta
8249 info/comments.
</p
>
8251 <p
>How to do this, you ask? Well, one create a new script
8252 /lib/init/init-d-script looking something like this:
8254 <p
><pre
>
8257 # Define LSB log_* functions.
8258 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
8259 # and status_of_proc is working.
8260 . /lib/lsb/init-functions
8263 # Function that starts the daemon/service
8269 #
0 if daemon has been started
8270 #
1 if daemon was already running
8271 #
2 if daemon could not be started
8272 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
8274 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
8277 # Add code here, if necessary, that waits for the process to be ready
8278 # to handle requests from services started subsequently which depend
8279 # on this one. As a last resort, sleep for some time.
8283 # Function that stops the daemon/service
8288 #
0 if daemon has been stopped
8289 #
1 if daemon was already stopped
8290 #
2 if daemon could not be stopped
8291 # other if a failure occurred
8292 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
8293 RETVAL=
"$?
"
8294 [
"$RETVAL
" =
2 ]
&& return
2
8295 # Wait for children to finish too if this is a daemon that forks
8296 # and if the daemon is only ever run from this initscript.
8297 # If the above conditions are not satisfied then add some other code
8298 # that waits for the process to drop all resources that could be
8299 # needed by services started subsequently. A last resort is to
8300 # sleep for some time.
8301 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
8302 [
"$?
" =
2 ]
&& return
2
8303 # Many daemons don
't delete their pidfiles when they exit.
8305 return
"$RETVAL
"
8309 # Function that sends a SIGHUP to the daemon/service
8313 # If the daemon can reload its configuration without
8314 # restarting (for example, when it is sent a SIGHUP),
8315 # then implement that here.
8317 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
8322 scriptbasename=
"$(basename $
1)
"
8323 echo
"SN: $scriptbasename
"
8324 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
8325 script=
"$
1"
8332 NAME=$(basename $DAEMON)
8333 PIDFILE=/var/run/$NAME.pid
8335 # Exit if the package is not installed
8336 #[ -x
"$DAEMON
" ] || exit
0
8338 # Read configuration variable file if it is present
8339 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
8341 # Load the VERBOSE setting and other rcS variables
8344 case
"$
1" in
8346 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
8348 case
"$?
" in
8349 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
8350 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
8354 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
8356 case
"$?
" in
8357 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
8358 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
8362 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
8364 #reload|force-reload)
8366 # If do_reload() is not implemented then leave this commented out
8367 # and leave
'force-reload
' as an alias for
'restart
'.
8369 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
8373 restart|force-reload)
8375 # If the
"reload
" option is implemented then remove the
8376 #
'force-reload
' alias
8378 log_daemon_msg
"Restarting $DESC
" "$NAME
"
8380 case
"$?
" in
8383 case
"$?
" in
8385 1) log_end_msg
1 ;; # Old process is still running
8386 *) log_end_msg
1 ;; # Failed to start
8396 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
8402 </pre
></p
>
8404 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
8405 lot. I did not really polish the approach, so it might not always
8406 work out of the box, but you get the idea. I did not try very hard to
8407 optimize it nor make it more robust either.
</p
>
8409 <p
>A better argument for switching init system in Debian than reducing
8410 the size of init scripts (which is a good thing to do anyway), is to
8411 get boot system that is able to handle the kernel events sensibly and
8412 robustly, and do not depend on the boot to run sequentially. The boot
8413 and the kernel have not behaved sequentially in years.
</p
>
8418 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
8419 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
8420 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
8421 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
8422 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
8423 remote display access is the preferred solution with oVirt and RedHat
8424 Enterprise Virtualization, and I was sad to discover the other day
8425 that the browser plugin needed to use these systems seamlessly was
8426 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
8427 for a package
</a
> was from
2012-
04-
10 with no progress since
8428 2013-
04-
01, so I decided to wrap up a package based on the great work
8429 from Cajus Pollmeier and put it in a collab-maint maintained git
8430 repository to get a package I could use. I would very much like
8431 others to help me maintain the package (or just take over, I do not
8432 mind), but as no-one had volunteered so far, I just uploaded it to
8433 NEW. I hope it will be available in Debian in a few days.
</p
>
8435 <p
>The source is now available from
8436 <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
>
8441 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
8442 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
8443 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
8444 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
8445 <description><p
>The
8446 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
8447 program is a a very nice system to create virtual machine images. It
8448 create a image file, add a partition table, mount it and run
8449 debootstrap in the mounted directory to create a Debian system on a
8450 stick. Yesterday, I decided to try to teach it how to make images for
8451 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
8452 of a plan to simplify the build system for
8453 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
8454 project
</a
>. The FreedomBox project already uses vmdebootstrap for
8455 the virtualbox images, but its current build system made multistrap
8456 based system for Dreamplug images, and it is lacking support for
8457 Raspberry Pi.
</p
>
8459 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
8460 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
8461 code and adjusted it to be able to build armel images on my amd64
8462 Debian laptop. I ended up giving vmdebootstrap five new options,
8463 allowing me to replicate the image creation process I use to make
8464 <a href=
"https://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
8465 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
8466 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
8467 call debootstrap with --foreign and to copy the handler into the
8468 generated chroot before running the second stage. This allow
8469 vmdebootstrap to create armel images on an amd64 host. Next I added
8470 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
8471 fstype
</tt
> to teach it to create a separate /boot/ partition with the
8472 given file system type, allowing me to create an image with a vfat
8473 partition for the /boot/ stuff. I also added a
<tt
>--variant
8474 variant
</tt
> option to allow me to create smaller images without the
8475 Debian base system packages installed. Finally, I added an option
8476 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
8477 as a boot loader. It is not needed on the Raspberry Pi and probably
8478 most other non-x86 architectures. The changes were accepted by the
8479 upstream author of vmdebootstrap yesterday and today, and is now
8481 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
8482 upstream project page
</a
>.
</p
>
8484 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
8485 create a small script (the customize script) to add the non-free
8486 binary blob needed to boot the Raspberry Pi and the APT source
8489 <p
><pre
>
8491 set -e # Exit on first error
8492 rootdir=
"$
1"
8493 cd
"$rootdir
"
8494 cat
&lt;
&lt;EOF
> etc/apt/sources.list
8495 deb http://http.debian.net/debian/ jessie main contrib non-free
8497 # Install non-free binary blob needed to boot Raspberry Pi. This
8498 # install a kernel somewhere too.
8499 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
8500 -O $rootdir/usr/bin/rpi-update
8501 chmod a+x $rootdir/usr/bin/rpi-update
8502 mkdir -p $rootdir/lib/modules
8503 touch $rootdir/boot/start.elf
8504 chroot $rootdir rpi-update
8505 </pre
></p
>
8507 <p
>Next, fetch the latest vmdebootstrap script and call it like this
8508 to build the image:
</p
>
8511 sudo ./vmdebootstrap \
8514 --distribution jessie \
8515 --mirror http://http.debian.net/debian \
8524 --root-password raspberry \
8525 --hostname raspberrypi \
8526 --foreign /usr/bin/qemu-arm-static \
8527 --customize `pwd`/customize \
8529 --package git-core \
8530 --package binutils \
8531 --package ca-certificates \
8534 </pre
></p
>
8536 <p
>The list of packages being installed are the ones needed by
8537 rpi-update to make the image bootable on the Raspberry Pi, with the
8538 exception of netbase, which is needed by debootstrap to find
8539 /etc/hosts with the minbase variant. I really wish there was a way to
8540 set up an Raspberry Pi using only packages in the Debian archive, but
8541 that is not possible as far as I know, because it boots from the GPU
8542 using a non-free binary blob.
</p
>
8544 <p
>The build host need debootstrap, kpartx and qemu-user-static and
8545 probably a few others installed. I have not checked the complete
8546 build dependency list.
</p
>
8548 <p
>The resulting image will not use the hardware floating point unit
8549 on the Raspberry PI, because the armel architecture in Debian is not
8550 optimized for that use. So the images created will be a bit slower
8551 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
8556 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
8557 <link>https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</link>
8558 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</guid>
8559 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
8560 <description><p
>The last few days I came across a few good causes that should get
8561 wider attention. I recommend signing and donating to each one of
8564 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
8565 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
8566 Women program which is a Google Summer of Code like initiative to get
8567 more women involved in free software. One debian sponsor has offered
8568 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
8569 earmarked
</a
> for this initiative. I donated a few minutes ago, and
8570 hope you will to. :)
</p
>
8572 <p
>And the Electronic Frontier Foundation just announced plans to
8573 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
8574 documentaries about the excessive spying
</a
> on every Internet user that
8575 take place these days, and their need to fund the work. I
've already
8576 donated. Are you next?
</p
>
8578 <p
>For my Norwegian audience, the organisation Studentenes og
8579 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
8580 statement under the heading
8581 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
8582 Access
</a
> for those of us asking for more focus on open access in the
8583 Norwegian government. So far
499 signatures. I hope you will sign it
8589 <title>Videos about the Freedombox project - for inspiration and learning
</title>
8590 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
8591 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
8592 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
8593 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
8594 project
</a
> have been going on for a while, and have presented the
8595 vision, ideas and solution several places. Here is a little
8596 collection of videos of talks and presentation of the project.
</p
>
8600 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
8601 2,
5 minute marketing film
</a
> (Youtube)
</li
>
8603 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
8604 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
8606 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
8607 Freedom in the Cloud - Software Freedom, Privacy and and Security for
8608 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
8609 (Youtube)
</li
>
8611 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
8612 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
8614 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
8615 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
8617 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
8618 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
8619 York City in
2012</a
> (Youtube)
</li
>
8621 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
8622 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
8623 (Youtube)
</li
>
8625 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
8626 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
8628 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
8629 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
8631 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
8632 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
8633 2013</a
> (Youtube)
</li
>
8637 <p
>A larger list is available from
8638 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
8639 Freedombox Wiki
</a
>.
</p
>
8641 <p
>On other news, I am happy to report that Freedombox based on Debian
8642 Jessie is coming along quite well, and soon both Owncloud and using
8643 Tor should be available for testers of the Freedombox solution. :) In
8644 a few weeks I hope everything needed to test it is included in Debian.
8645 The withsqlite package is already in Debian, and the plinth package is
8646 pending in NEW. The third and vital part of that puzzle is the
8647 metapackage/setup framework, which is still pending an upload. Join
8648 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
8649 (#freedombox on irc.debian.org)
</a
> and
8650 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
8651 mailing list
</a
> if you want to help make this vision come true.
</p
>
8656 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
8657 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
8658 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
8659 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
8660 <description><p
>I was introduced to the
8661 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
8662 in
2010, when Eben Moglen presented his vision about serving the need
8663 of non-technical people to keep their personal information private and
8664 within the legal protection of their own homes. The idea is to give
8665 people back the power over their network and machines, and return
8666 Internet back to its intended peer-to-peer architecture. Instead of
8667 depending on a central service, the Freedombox will give everyone
8668 control over their own basic infrastructure.
</p
>
8670 <p
>I
've intended to join the effort since then, but other tasks have
8671 taken priority. But this summers nasty news about the misuse of trust
8672 and privilege exercised by the
"western
" intelligence gathering
8673 communities increased my eagerness to contribute to a point where I
8674 actually started working on the project a while back.
</p
>
8676 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
8677 Debian initiative
</a
> based on the vision from Eben Moglen, is to
8678 create a simple and cheap Debian based appliance that anyone can hook
8679 up in their home and get access to secure and private services and
8680 communication. The initial deployment platform have been the
8681 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
8682 which is a piece of hardware I do not own. So to be able to test what
8683 the current Freedombox setup look like, I had to come up with a way to install
8684 it on some hardware I do have access to. I have rewritten the
8685 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
8686 image build framework to use .deb packages instead of only copying
8687 setup into the boot images, and thanks to this rewrite I am able to
8688 set up any machine supported by Debian Wheezy as a Freedombox, using
8689 the previously mentioned deb (and a few support debs for packages
8690 missing in Debian).
</p
>
8692 <p
>The current Freedombox setup consist of a set of bootstrapping
8694 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
8695 and a administrative web interface
8696 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
8697 withsqlite), as well as a privacy enhancing proxy based on
8698 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
8699 (freedombox-privoxy). There is also a web/javascript based XMPP
8700 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
8701 trying (unsuccessfully so far) to talk to the XMPP server
8702 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
8703 web interface is pluggable, and the goal is to use it to enable OpenID
8704 services, mesh network connectivity, use of TOR, etc, etc. Not much of
8705 this is really working yet, see
8706 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
8707 project TODO
</a
> for links to GIT repositories. Most of the code is
8708 on github at the moment. The HTTP proxy is operational out of the
8709 box, and the admin web interface can be used to add/remove plinth
8710 users. I
've not been able to do anything else with it so far, but
8711 know there are several branches spread around github and other places
8712 with lots of half baked features.
</p
>
8714 <p
>Anyway, if you want to have a look at the current state, the
8715 following recipes should work to give you a test machine to poke
8718 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
8722 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
8723 <li
>Boot from it, either as CD or USB stick.
</li
>
8724 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
8725 to the Debian installer:
<p
>
8726 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
8728 <li
>Answer the few language/region/password questions and pick disk to
8729 install on.
</li
>
8731 <li
>When the installation is finished and the machine have rebooted a
8732 few times, your Freedombox is ready for testing.
</li
>
8736 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
8740 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
8741 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
8742 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
8744 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
8745 </pre
></li
>
8746 <li
><p
>Run this as root:
</p
>
8748 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
8751 apt-get install freedombox-setup
8752 /usr/lib/freedombox/setup
8753 </pre
></li
>
8754 <li
>Reboot into your freshly created Freedombox.
</li
>
8758 <p
>You can test it on other architectures too, but because the
8759 freedombox-privoxy package is binary, it will only work as intended on
8760 the architectures where I have had time to build the binary and put it
8761 in my APT repository. But do not let this stop you. It is only a
8762 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
8764 <p
>Note that by default Freedombox is a DHCP server on the
8765 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
8766 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
8767 disable
</tt
>" as root.
</p
>
8769 <p
>Please let me know if this works for you, or if you have any
8770 problems. We gather on the IRC channel
8771 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
8772 irc.debian.org and the
8773 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
8774 mailing list
</a
>.
</p
>
8776 <p
>Once you get your freedombox operational, you can visit
8777 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
8778 welcome screen (dead end - do not be surprised if you are unable to
8779 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
8780 to look at the rest of plinth. The default user is
'admin
' and the
8781 default password is
'secret
'.
</p
>
8786 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
8787 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
8788 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
8789 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
8790 <description><p
>Earlier, I reported about
8791 <a href=
"https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
8792 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
8793 told by IBM that the original disk should be thrown away. And as
8794 there no longer was a problem if I bricked the firmware, I decided
8795 today to try to install Intel firmware to replace the Lenovo firmware
8796 currently on the disk.
</p
>
8798 <p
>I searched the Intel site for firmware, and found
8799 <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
>
8800 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
8801 according to the site should contain the latest firmware for SSD
8802 disks. I inserted the broken disk in one of my spare laptops and
8803 booted the ISO from a USB stick. The disk was recognized, but the
8804 program claimed the newest firmware already were installed and refused
8805 to insert any Intel firmware. So no change, and the disk is still
8806 unable to handle write load. :( I guess the only way to get them
8807 working would be if Lenovo releases new firmware. No idea how likely
8808 that is. Anyway, just blogging about this test for completeness. I
8809 got a working Samsung disk, and see no point in spending more time on
8810 the broken disks.
</p
>
8815 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
8816 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
8817 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
8818 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
8819 <description><p
>Today I switched to
8820 <a href=
"https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
8821 new laptop
</a
>. I
've previously written about the problems I had with
8822 my new Thinkpad X230, which was delivered with an
8823 <a href=
"https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
">180
8824 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
8825 sustained writes. My hardware supplier have been very forthcoming in
8826 trying to find a solution, and after first trying with another
8827 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
8828 disk instead to fix it once and for all. The Samsung disk survived
8829 the installation of Debian with encrypted disks (filling the disk with
8830 random data during installation killed the first two), and I thus
8831 decided to trust it with my data. I have installed it as a Debian Edu
8832 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
8833 server at home using Kerberos and LDAP, and will use it as my work
8834 station from now on.
</p
>
8836 <p
>As this is a solid state disk with no moving parts, I believe the
8837 Debian Wheezy default installation need to be tuned a bit to increase
8838 performance and increase life time of the disk. The Linux kernel and
8839 user space applications do not yet adjust automatically to such
8840 environment. To make it easier for my self, I created a draft Debian
8841 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
8842 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
8843 for the ssd-setup package
</a
> is available from collab-maint, and it
8844 is set up to adjust the setup of the machine by just installing the
8845 package. If there is any non-SSD disk in the machine, the package
8846 will refuse to install, as I did not try to write any logic to sort
8847 file systems in SSD and non-SSD file systems.
</p
>
8849 <p
>I consider the package a draft, as I am a bit unsure how to best
8850 set up Debian Wheezy with an SSD. It is adjusted to my use case,
8851 where I set up the machine with one large encrypted partition (in
8852 addition to /boot), put LVM on top of this and set up partitions on
8853 top of this again. See the README file in the package source for the
8854 references I used to pick the settings. At the moment these
8855 parameters are tuned:
</p
>
8859 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
8860 (adding discard to /etc/crypttab)
</li
>
8862 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
8863 this case a cryptsetup partition) by changing issue_discards from
8864 0 to
1 in /etc/lvm/lvm.conf.
</li
>
8866 <li
>Set relatime as a file system option for ext3 and ext4 file
8869 <li
>Tell swap to use TRIM commands by adding
'discard
' to
8870 /etc/fstab.
</li
>
8872 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
8874 <li
>Run fstrim on every ext3 and ext4 file system every night (from
8875 cron.daily).
</li
>
8877 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
8878 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
8882 <p
>During installation, I cancelled the part where the installer fill
8883 the disk with random data, as this would kill the SSD performance for
8884 little gain. My goal with the encrypted file system is to ensure
8885 those stealing my laptop end up with a brick and not a working
8886 computer. I have no hope in keeping the really resourceful people
8887 from getting the data on the disk (see
8888 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
8889 Thus I concluded that adding the discard option to crypttab is the
8890 right thing to do.
</p
>
8892 <p
>I considered using the noop I/O scheduler, as several recommended
8893 it for SSD, but others recommended deadline and a benchmark I found
8894 indicated that deadline might be better for interactive use.
</p
>
8896 <p
>I also considered using the
'discard
' file system option for ext3
8897 and ext4, but read that it would give a performance hit ever time a
8898 file is removed, and thought it best to that that slowdown once a day
8899 instead of during my work.
</p
>
8901 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
8902 this is already done by Debian Edu.
</p
>
8904 <p
>I have not yet started on the user space tuning. I expect
8905 iceweasel need some tuning, and perhaps other applications too, but
8906 have not yet had time to investigate those parts.
</p
>
8908 <p
>The package should work on Ubuntu too, but I have not yet tested it
8911 <p
>As for the answer to the question in the title of this blog post,
8912 as far as I know, the only solution I know about is to replace the
8913 disk. It might be possible to flash it with Intel firmware instead of
8914 the Lenovo firmware. But I have not tried and did not want to do so
8915 without approval from Lenovo as I wanted to keep the warranty on the
8916 disk until a solution was found and they wanted the broken disks
8922 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
8923 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
8924 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</guid>
8925 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
8926 <description><p
>A few days ago, I wrote about
8927 <a href=
"https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
8928 problems I experienced with my new X230 and its SSD disk
</a
>, which
8929 was dying during installation because it is unable to cope with
8930 sustained write. My supplier is in contact with
8931 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
8932 replacement disk to try to fix the problem. They decided to send an
8933 identical model, so my hopes for a permanent fix was slim.
</p
>
8935 <p
>Anyway, today I got the replacement disk and tried to install
8936 Debian Edu Wheezy with encrypted disk on it. The new disk have the
8937 same firmware version as the original. This time my hope raised
8938 slightly as the installation progressed, as the original disk used to
8939 die after
4-
7% of the disk was written to, while this time it kept
8940 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
8941 died again and I was back on square one. I still do not have a new
8942 laptop with a disk I can trust. I can not live with a disk that might
8943 lock up when I download a new
8944 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
8945 other large files. I look forward to hearing from my supplier with
8946 the next proposal from Lenovo.
</p
>
8948 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
8949 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
8950 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8951 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
8952 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8953 P/N
45N8295, P0C38732.
</p
>
8955 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
8956 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
8957 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8958 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
8959 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8960 P/N
45N8295, P0C38732.
</p
>
8962 <p
>The only difference is in the first number (serial number?), ISN,
8963 SA, date and WNPP values. Mentioning all the details here in case
8964 someone is able to use the information to find a way to identify the
8965 failing disk among working ones (if any such working disk actually
8971 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
8972 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
8973 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
8974 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
8975 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
8976 Debian Edu developer gathering and Debian and Ubuntu bug squashing
8977 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
8978 member assosiation NUUG
</a
> and
8979 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
8980 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
8981 Bitraf
</a
>.
</p
>
8983 <p
>It starts
10:
00 and continue until late evening. Everyone is
8984 welcome, and there is no fee to participate. There is on the other
8985 hand limited space, and only room for
30 people. Please put your name
8986 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
8987 wiki page
</a
> if you plan to join us.
</p
>
8992 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
8993 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
8994 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
8995 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
8996 <description><p
>Half a year ago, I reported that I had to find a
8997 <a href=
"https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
8998 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
8999 time to spend on it, and it took a while to find a model I believe
9000 will do the job, but two days ago the replacement finally arrived. I
9002 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
9003 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
9004 a roaming workstation, and it seemed to work flawlessly. But my
9005 second installation with encrypted disk was not as successful. More
9006 on that below.
</p
>
9008 <p
>I had a hard time trying to track down a good laptop, as my most
9009 important requirements (robust and with a good keyboard) are never
9010 listed in the feature list. But I did get good help from the search
9011 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
9012 allowed me to limit the list of interesting laptops based on my other
9013 requirements. A bit surprising that SSD disk are not disks according
9014 to that search interface, so I had to drop specifying the number of
9015 disks from my search parameters. I also asked around among friends to
9016 get their impression on keyboards and robustness.
</p
>
9018 <p
>So the new laptop arrived, and it is quite a lot wider than the
9019 X41. I am not quite convinced about the keyboard, as it is
9020 significantly wider than my old keyboard, and I have to stretch my
9021 hand a lot more to reach the edges. But the key response is fairly
9022 good and the individual key shape is fairly easy to handle, so I hope
9023 I will get used to it. My old X40 was starting to fail, and I really
9024 needed a new laptop now. :)
</p
>
9026 <p
>Turning off the touch pad was simple. All it took was a quick
9027 visit to the BIOS during boot it disable it.
</p
>
9029 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
9030 lock up during load. And this happen when installing Debian Wheezy
9031 with encrypted disk, while the disk is being filled with random data.
9032 I also tested to install Ubuntu Raring, and it happen there too if I
9033 reenable the code to fill the disk with random data (it is disabled by
9034 default in Ubuntu). And the bug with is already known. It was
9035 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
9036 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
9037 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
9038 kernel developers as
9039 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
9040 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
9041 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
9042 Lenovo forums, both for
9043 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
9044 2012-
11-
10</a
> and for
9045 <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
9046 03-
20-
2013</a
>. The problem do not only affect installation. The
9047 reports state that the disk lock up during use if many writes are done
9048 on the disk, so it is much no use to work around the installation
9049 problem and end up with a computer that can lock up at any moment.
9051 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
9052 available
</a
> that will lock up the hard drive after running a few
9053 minutes by writing to a file.
</p
>
9055 <p
>I
've contacted my supplier and asked how to handle this, and after
9056 contacting PCHELP Norway (request
01D1FDP) which handle support
9057 requests for Lenovo, his first suggestion was to upgrade the disk
9058 firmware. Unfortunately there is no newer firmware available from
9059 Lenovo, as my disk already have the most recent one (version LF1i). I
9060 hope to hear more from him today and hope the problem can be
9066 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
9067 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
9068 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
9069 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
9070 <description><p
>Half a year ago, I reported that I had to find a replacement for my
9071 trusty old Thinkpad X41. Unfortunately I did not have much time to
9072 spend on it, but today the replacement finally arrived. I ended up
9073 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
9074 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
9075 Wheezy as a roaming workstation, and it worked flawlessly. As I write
9076 this, it is installing what I hope will be a more final installation,
9077 with a encrypted hard drive to ensure any dope head stealing it end up
9078 with an expencive door stop.
</p
>
9080 <p
>I had a hard time trying to track down a good laptop, as my most
9081 important requirements (robust and with a good keyboard) are never
9082 listed in the feature list. But I did get good help from the search
9083 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
9084 allowed me to limit the list of interesting laptops based on my other
9085 requirements. A bit surprising that SSD disk are not disks, so I had
9086 to drop number of disks from my search parameters.
</p
>
9088 <p
>I am not quite convinced about the keyboard, as it is significantly
9089 wider than my old keyboard, and I have to stretch my hand a lot more
9090 to reach the edges. But the key response is fairly good and the
9091 individual key shape is fairly easy to handle, so I hope I will get
9092 used to it. My old X40 was starting to fail, and I really needed a
9093 new laptop now. :)
</p
>
9095 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
9100 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
9101 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
9102 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
9103 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
9104 <description><p
>It annoys me when the computer fail to do automatically what it is
9105 perfectly capable of, and I have to do it manually to get things
9106 working. One such task is to find out what firmware packages are
9107 needed to get the hardware on my computer working. Most often this
9108 affect the wifi card, but some times it even affect the RAID
9109 controller or the ethernet card. Today I pushed version
0.4 of the
9110 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
9111 including a new script isenkram-autoinstall-firmware handling the
9112 process of asking all the loaded kernel modules what firmware files
9113 they want, find debian packages providing these files and install the
9114 debian packages. Here is a test run on my laptop:
</p
>
9116 <p
><pre
>
9117 # isenkram-autoinstall-firmware
9118 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
9119 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
9120 info: locating packages with the requested firmware files
9121 info: Updating APT sources after adding non-free APT source
9122 info: trying to install firmware-ipw2x00
9125 Preconfiguring packages ...
9126 Selecting previously deselected package firmware-ipw2x00.
9127 (Reading database ...
259727 files and directories currently installed.)
9128 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
9129 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
9131 </pre
></p
>
9133 <p
>When all the requested firmware is present, a simple message is
9134 printed instead:
</p
>
9136 <p
><pre
>
9137 # isenkram-autoinstall-firmware
9138 info: did not find any firmware files requested by loaded kernel modules. exiting
9140 </pre
></p
>
9142 <p
>It could use some polish, but it is already working well and saving
9143 me some time when setting up new machines. :)
</p
>
9145 <p
>So, how does it work? It look at the set of currently loaded
9146 kernel modules, and look up each one of them using modinfo, to find
9147 the firmware files listed in the module meta-information. Next, it
9148 download the Contents file from a nearby APT mirror, and search for
9149 the firmware files in this file to locate the package with the
9150 requested firmware file. If the package is in the non-free section, a
9151 non-free APT source is added and the package is installed using
9152 <tt
>apt-get install
</tt
>. The end result is a slightly better working
9155 <p
>I hope someone find time to implement a more polished version of
9156 this script as part of the hw-detect debian-installer module, to
9157 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
9158 #
655507</a
>. There really is no need to insert USB sticks with
9159 firmware during a PXE install when the packages already are available
9160 from the nearby Debian mirror.
</p
>
9165 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
9166 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
9167 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
9168 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
9169 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
9170 the screen just turn black when Linux boot, either during installation
9171 or on first boot from the hard disk. I
've seen it once in a while the
9172 last few years, but only recently understood the cause. I
've seen it
9173 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
9174 The reason seem to be in the wiring of some laptops. The system to
9175 control the screen background light is inverted, so when Linux try to
9176 turn the brightness fully on, it end up turning it off instead. I do
9177 not know which Linux drivers are affected, but this post is about the
9178 i915 driver used by the
9179 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
9180 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
9182 <p
>The problem can be worked around two ways. Either by adding
9183 i915.invert_brightness=
1 as a kernel option, or by adding a file in
9184 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
9185 option when it load the i915 kernel module. On Debian and Ubuntu, it
9186 can be done by running these commands as root:
</p
>
9189 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
9190 update-initramfs -u -k all
9193 <p
>Since March
2012 there is
9194 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
9195 mechanism in the Linux kernel
</a
> to tell the i915 driver which
9196 hardware have this problem, and get the driver to invert the
9197 brightness setting automatically. To use it, one need to add a row in
9198 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
9199 intel_quirks array
</a
> in the driver source
9200 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
9201 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
9202 number (vendor number
8086 is assumed) and subdevice vendor and device
9205 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
9206 -vvnn
</tt
> for the video card in question:
</p
>
9208 <p
><pre
>
9209 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
9210 3rd Gen Core processor Graphics Controller [
8086:
0156] \
9211 (rev
09) (prog-if
00 [VGA controller])
9212 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
9213 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
9214 ParErr- Stepping- SE RR- FastB2B- DisINTx+
9215 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
9216 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
9218 Interrupt: pin A routed to IRQ
42
9219 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
9220 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
9221 Region
4: I/O ports at
4000 [size=
64]
9222 Expansion ROM at
<unassigned
> [disabled]
9223 Capabilities:
<access denied
>
9224 Kernel driver in use: i915
9225 </pre
></p
>
9227 <p
>The resulting intel_quirks entry would then look like this:
</p
>
9229 <p
><pre
>
9230 struct intel_quirk intel_quirks[] = {
9232 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
9233 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
9236 </pre
></p
>
9238 <p
>According to the kernel module instructions (as seen using
9239 <tt
>modinfo i915
</tt
>), information about hardware needing the
9240 invert_brightness flag should be sent to the
9241 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
9242 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
9243 developers. But my email about the laptop sent
2013-
06-
03 have not
9245 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
9246 web archive for the mailing list
</a
>, so I suspect they do not accept
9247 emails from non-subscribers. Because of this, I sent my patch also to
9248 the Debian bug tracking system instead as
9249 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
9250 sure the patch is not lost.
</p
>
9252 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
9253 with this problem working properly with Linux. If you use Gnome, your
9254 worries should be over at this point. But if you use KDE, there is
9255 something in KDE ignoring the invert_brightness setting and turning on
9256 the screen during login. I
've reported it to Debian as
9257 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
9258 have no idea yet how to figure out exactly what subsystem is doing
9259 this. Perhaps you can help? Perhaps you know what the Gnome
9260 developers did to handle this, and this can give a clue to the KDE
9261 developers? Or you know where in KDE the screen brightness is changed
9262 during login? If so, please update the BTS report (or get in touch if
9263 you do not know how to update BTS).
</p
>
9265 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
9266 acpi_backlight=vendor, to disable ACPI backlight support completely,
9267 as the ACPI information on the machine is trash and it is better to
9268 leave it to the intel video driver to control the screen
9269 backlight.
</p
>
9274 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
9275 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
9276 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</guid>
9277 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
9278 <description><p
>Two days ago, I asked
9279 <a href=
"https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
">how
9280 I could install Linux on a Packard Bell EasyNote LV computer
9281 preinstalled with Windows
8</a
>. I found a solution, but am horrified
9282 with the obstacles put in the way of Linux users on a laptop with UEFI
9283 and Windows
8.
</p
>
9285 <p
>I never found out if the cause of my problems were the use of UEFI
9286 secure booting or fast boot. I suspect fast boot was the problem,
9287 causing the firmware to boot directly from HD without considering any
9288 key presses and alternative devices, but do not know UEFI settings
9289 enough to tell.
</p
>
9291 <p
>There is no way to install Linux on the machine in question without
9292 opening the box and disconnecting the hard drive! This is as far as I
9293 can tell, the only way to get access to the firmware setup menu
9294 without accepting the Windows
8 license agreement. I am told (and
9295 found description on how to) that it is possible to configure the
9296 firmware setup once booted into Windows
8. But as I believe the terms
9297 of that agreement are completely unacceptable, accepting the license
9298 was never an alternative. I do not enter agreements I do not intend
9299 to follow.
</p
>
9301 <p
>I feared I had to return the laptops and ask for a refund, and
9302 waste many hours on this, but luckily there was a way to get it to
9303 work. But I would not recommend it to anyone planning to run Linux on
9304 it, and I have become sceptical to Windows
8 certified laptops. Is
9305 this the way Linux will be forced out of the market place, by making
9306 it close to impossible for
"normal
" users to install Linux without
9307 accepting the Microsoft Windows license terms? Or at least not
9308 without risking to loose the warranty?
</p
>
9310 <p
>I
've updated the
9311 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
9312 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
9313 do not have to struggle as much as I did to get Linux into the
9316 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
9317 Michael Tokarev and others for feedback and ideas.
</p
>
9322 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
9323 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
9324 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</guid>
9325 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
9326 <description><p
>I
've run into quite a problem the last few days. I bought three
9327 new laptops for my parents and a few others. I bought Packard Bell
9328 Easynote LV to run Kubuntu on and use as their home computer. But I
9329 am completely unable to figure out how to install Linux on it. The
9330 computer is preinstalled with Windows
8, and I suspect it uses UEFI
9331 instead of a BIOS to boot.
</p
>
9333 <p
>The problem is that I am unable to get it to PXE boot, and unable
9334 to get it to boot the Linux installer from my USB stick. I have yet
9335 to try the DVD install, and still hope it will work. when I turn on
9336 the computer, there is no information on what buttons to press to get
9337 the normal boot menu. I expect to get some boot menu to select PXE or
9338 USB stick booting. When booting, it first ask for the language to
9339 use, then for some regional settings, and finally if I will accept the
9340 Windows
8 terms of use. As these terms are completely unacceptable to
9341 me, I have no other choice but to turn off the computer and try again
9342 to get it to boot the Linux installer.
</p
>
9344 <p
>I have gathered my findings so far on a Linlap page about the
9345 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
9346 EasyNote LV
</a
> model. If you have any idea how to get Linux
9347 installed on this machine, please get in touch or update that wiki
9348 page. If I can
't find a way to install Linux, I will have to return
9349 the laptop to the seller and find another machine for my parents.
</p
>
9351 <p
>I wonder, is this the way Linux will be forced out of the market
9352 using UEFI and
"secure boot
" by making it impossible to install Linux
9353 on new Laptops?
</p
>
9358 <title>How to transform a Debian based system to a Debian Edu installation
</title>
9359 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
9360 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
9361 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
9362 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
9363 an operating system based on Debian intended for use in schools. It
9364 contain a turn-key solution for the computer network provided to
9365 pupils in the primary schools. It provide both the central server,
9366 network boot servers and desktop environments with heaps of
9367 educational software. The project was founded almost
12 years ago,
9368 2001-
07-
02. If you want to support the project, which is in need for
9369 cash to fund developer gatherings and other project related activity,
9370 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
9371 donate some money
</a
>.
9373 <p
>A topic that come up again and again on the Debian Edu mailing
9374 lists and elsewhere, is the question on how to transform a Debian or
9375 Ubuntu installation into a Debian Edu installation. It isn
't very
9376 hard, and last week I wrote a script to replicate the steps done by
9377 the Debian Edu installer.
</p
>
9379 <p
>The script,
9380 <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/
>
9381 in the debian-edu-config package, will go through these six steps and
9382 transform an existing Debian Wheezy or Ubuntu (untested) installation
9383 into a Debian Edu Workstation:
</p
>
9387 <li
>Add skolelinux related APT sources.
</li
>
9388 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
9389 <li
>Install debian-edu-install to load preseeding values and pull in
9390 our configuration.
</li
>
9391 <li
>Preseed debconf database with profile setup in
9392 /etc/debian-edu/config, and run tasksel to install packages
9393 according to the profile specified in the config above,
9394 overriding some of the Debian automation machinery.
</li
>
9395 <li
>Run debian-edu-cfengine-D installation to configure everything
9396 that could not be done using preseeding.
</li
>
9397 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
9401 <p
>There are some steps in the Debian Edu installation that can not be
9402 replicated like this. Disk partitioning and LVM setup, for example.
9403 So this script just assume there is enough disk space to install all
9404 the needed packages.
</p
>
9406 <p
>The script was created to help a Debian Edu student working on
9407 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
9408 Debian Edu client, and using it he can take the existing
9409 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
9410 transform it into a fully functioning Debian Edu Workstation (or
9411 Roaming Workstation, or whatever :).
</p
>
9413 <p
>The default setting in the script is to create a KDE Workstation.
9414 If a LXDE based Roaming workstation is wanted instead, modify the
9415 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
9417 <p
><pre
>
9418 PROFILE=
"Roaming-Workstation
"
9419 DESKTOP=
"lxde
"
9420 </pre
></p
>
9422 <p
>The script could even become useful to set up Debian Edu servers in
9423 the cloud, by starting with a virtual Debian installation at some
9424 virtual hosting service and setting up all the services on first
9430 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
9431 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
9432 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
9433 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
9434 <description><P
>In January,
9435 <a href=
"https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
9436 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
9437 channel #debian-lego
</a
>, for those of us in the Debian and Linux
9438 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
9439 marvellous construction system from Denmark. We also created
9440 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
9441 a place to take notes and write down our plans and hopes. And several
9442 people showed up to help. I was very happy to see the effect of my
9443 call. Since the small start, we have a debtags tag
9444 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
9445 tag for LEGO related packages, and now count
10 packages related to
9446 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
9448 <p
><table
>
9449 <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
>
9450 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
9451 <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
>
9452 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
9453 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
9454 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
9455 <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
>
9456 <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
>
9457 <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
>
9458 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
9459 </table
></p
>
9461 <p
>Some of these are available in Wheezy, and all but one are
9462 currently available in Jessie/testing. leocad is so far only
9463 available in experimental.
</p
>
9465 <p
>If you care about LEGO in Debian, please join us on IRC and help
9466 adding the rest of the great free software tools available on Linux
9467 for LEGO designers.
</p
>
9472 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
9473 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
9474 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
9475 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
9476 <description><p
>When I woke up this morning, I was very happy to see that the
9477 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
9478 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
9479 Debian release, and I expect to move my machines at home over to it fairly
9482 <p
>The new debian release contain heaps of new stuff, and one program
9483 in particular make me very happy to see included. The
9484 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
9485 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
9486 included for the first time. Alongside similar programs like
9487 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
9488 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
9489 it allow for visual programming where syntax errors can not happen,
9490 and a friendly programming environment for learning to control the
9491 computer. Scratch will also be included in the next release of Debian
9494 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
9495 Edu/Skolelinux release too. The
9496 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
9497 alpha release
</a
> went out last week, and the next should soon
9503 <title>Isenkram
0.2 finally in the Debian archive
</title>
9504 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
9505 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
9506 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
9507 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
9508 package
</a
> finally made it into the archive, after lingering in NEW
9509 for many months. I uploaded it to the Debian experimental suite
9510 2013-
01-
27, and today it was accepted into the archive.
</p
>
9512 <p
>Isenkram is a system for suggesting to users what packages to
9513 install to work with a pluggable hardware device. The suggestion pop
9514 up when the device is plugged in. For example if a Lego Mindstorm NXT
9515 is inserted, it will suggest to install the program needed to program
9516 the NXT controller. Give it a go, and report bugs and suggestions to
9522 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
9523 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
9524 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
9525 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
9526 <description><p
>My
9527 <a href=
"https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
9528 bitcoin related blog post
</a
> mentioned that the new
9529 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
9530 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
9531 2013-
01-
19, and have been available in unstable since then. It was
9532 automatically copied to Ubuntu, and is available in their Raring
9533 version too.
</p
>
9535 <p
>But there is a strange problem with the build that block this new
9536 version from being available on the i386 and kfreebsd-i386
9537 architectures. For some strange reason, the autobuilders in Debian
9538 for these architectures fail to run the test suite on these
9539 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
9540 We are so far unable to reproduce it when building it manually, and
9541 no-one have been able to propose a fix. If you got an idea what is
9542 failing, please let us know via the BTS.
</p
>
9544 <p
>One feature that is annoying me with of the bitcoin client, because
9545 I often run low on disk space, is the fact that the client will exit
9546 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
9547 #
696715</a
>). So make sure you have enough disk space when you run
9550 <p
>As usual, if you use bitcoin and want to show your support of my
9551 activities, please send Bitcoin donations to my address
9552 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9557 <title>Welcome to the world, Isenkram!
</title>
9558 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
9559 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
9560 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
9561 <description><p
>Yesterday, I
9562 <a href=
"https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
9563 for testers
</a
> for my prototype for making Debian better at handling
9564 pluggable hardware devices, which I
9565 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
9566 out to create
</a
> earlier this month. Several valuable testers showed
9567 up, and caused me to really want to to open up the development to more
9568 people. But before I did this, I want to come up with a sensible name
9569 for this project. Today I finally decided on a new name, and I have
9570 renamed the project from hw-support-handler to this new name. In the
9571 process, I moved the source to git and made it available as a
9572 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
9573 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
9574 To fetch and build the latest version of the source, use
</p
>
9577 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
9578 cd isenkram
&& git-buildpackage -us -uc
9581 <p
>I have not yet adjusted all files to use the new name yet. If you
9582 want to hack on the source or improve the package, please go ahead.
9583 But please talk to me first on IRC or via email before you do major
9584 changes, to make sure we do not step on each others toes. :)
</p
>
9586 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
9587 stuff, typically meaning tools, nails, screws, etc. Typical hardware
9588 stuff, in other words. I
've been told it is the Norwegian variant of
9589 the German word eisenkram, for those that are familiar with that
9592 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
9593 instructions, to avoid confusing people with an error from the signing
9596 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
9597 clone argument to avoid the need for authentication.
</p
>
9602 <title>First prototype ready making hardware easier to use in Debian
</title>
9603 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
9604 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
9605 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
9606 <description><p
>Early this month I set out to try to
9607 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
9608 the Debian support for pluggable hardware devices
</a
>. Now my
9609 prototype is working, and it is ready for a larger audience. To test
9611 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
9612 from the Debian Edu subversion repository
</a
>, build and install the
9613 package. You might have to log out and in again activate the
9614 autostart script.
</p
>
9616 <p
>The design is simple:
</p
>
9620 <li
>Add desktop entry in /usr/share/autostart/ causing a program
9621 hw-support-handlerd to start when the user log in.
</li
>
9623 <li
>This program listen for kernel events about new hardware (directly
9624 from the kernel like udev does), not using HAL dbus events as I
9625 initially did.
</li
>
9627 <li
>When new hardware is inserted, look up the hardware modalias in
9628 the APT database, a database
9629 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
9630 via HTTP
</a
> and a database available as part of the package.
</li
>
9632 <li
>If a package is mapped to the hardware in question, the package
9633 isn
't installed yet and this is the first time the hardware was
9634 plugged in, show a desktop notification suggesting to install the
9635 package or packages.
</li
>
9637 <li
>If the user click on the
'install package now
' button, ask
9638 aptdaemon via the PackageKit API to install the requrired package.
</li
>
9640 <li
>aptdaemon ask for root password or sudo password, and install the
9641 package while showing progress information in a window.
</li
>
9645 <p
>I still need to come up with a better name for the system. Here
9646 are some screen shots showing the prototype in action. First the
9647 notification, then the password request, and finally the request to
9648 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
9650 <p
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
9651 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
9652 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
9653 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
9654 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
9656 <p
>The prototype still need to be improved with longer timeouts, but
9657 is already useful. The database of hardware to package mappings also
9658 need more work. It is currently compatible with the Ubuntu way of
9659 storing such information in the package control file, but could be
9660 changed to use other formats instead or in addition to the current
9661 method. I
've dropped the use of discover for this mapping, as the
9662 modalias approach is more flexible and easier to use on Linux as long
9663 as the Linux kernel expose its modalias strings directly.
</p
>
9665 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
9666 here is the command required to check out and build the source: Use
9667 '<tt
>svn checkout
9668 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
9669 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
9670 devscripts package.
</p
>
9672 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
9673 renamed to Isenkram and the source moved from the Debian Edu
9674 subversion repository to a Debian collab-maint git repository. See
9675 <a href=
"https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
9676 instructions
</a
> for details.
</p
>
9681 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
9682 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
9683 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
9684 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
9685 <description><p
>This Christmas my trusty old laptop died. It died quietly and
9686 suddenly in bed. With a quiet whimper, it went completely quiet and
9687 black. The power button was no longer able to turn it on. It was a
9688 IBM Thinkpad X41, and the best laptop I ever had. Better than both
9689 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
9690 Compaq I had before that. Now I need to find a replacement. To keep
9691 going during Christmas, I moved the one year old SSD disk to my old
9692 X40 where it fitted (only one I had left that could use it), but it is
9693 not a durable solution.
9695 <p
>My laptop needs are fairly modest. This is my wishlist from when I
9696 got a new one more than
10 years ago. It still holds true.:)
</p
>
9700 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
9701 than A4).
</li
>
9702 <li
>Robust, it will be in my backpack every day.
</li
>
9703 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
9704 <li
>Long battery life time. Preferable a week.
</li
>
9705 <li
>Internal WIFI network card.
</li
>
9706 <li
>Internal Twisted Pair network card.
</li
>
9707 <li
>Some USB slots (
2-
3 is plenty)
</li
>
9708 <li
>Good keyboard - similar to the Thinkpad.
</li
>
9709 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
9711 <li
>Hardware supported by Debian Stable, ie the default kernel and
9712 X.org packages.
</li
>
9713 <li
>Quiet, preferably fan free (or at least not using the fan most of
9718 <p
>You will notice that there are no RAM and CPU requirements in the
9719 list. The reason is simply that the specifications on laptops the
9720 last
10-
15 years have been sufficient for my needs, and I have to look
9721 at other features to choose my laptop. But are there still made as
9722 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
9723 robust, and Thinkpads seem to be heading in the wrong direction since
9724 Lenovo took over. But I
've been told that X220 and X1 Carbon might
9725 still be useful.
</p
>
9727 <p
>Perhaps I should rethink my needs, and look for a pad with an
9728 external keyboard? I
'll have to check the
9729 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
9730 well-supported laptops, or perhaps just buy one preinstalled from one
9731 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
9732 Pre-loaded site
</a
>.
</p
>
9737 <title>How to find a browser plugin supporting a given MIME type
</title>
9738 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
9739 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
9740 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
9741 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
9742 install to get support for a given MIME type. Thanks to
9743 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
9744 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
9745 Unfortunately, not very many packages provide the needed meta
9746 information, Anyway, here is a small script to look up all browser
9747 plugin packages announcing ther MIME support using this specification:
</p
>
9753 def pkgs_handling_mimetype(mimetype):
9758 version = pkg.candidate
9760 version = pkg.installed
9763 record = version.record
9764 if not record.has_key(
'Npp-MimeType
'):
9766 mime_types = record[
'Npp-MimeType
'].split(
',
')
9767 for t in mime_types:
9768 t = t.rstrip().strip()
9770 thepkgs.append(pkg.name)
9772 mimetype =
"audio/ogg
"
9773 if
1 < len(sys.argv):
9774 mimetype = sys.argv[
1]
9775 print
"Browser plugin packages supporting %s:
" % mimetype
9776 for pkg in pkgs_handling_mimetype(mimetype):
9777 print
" %s
" %pkg
9780 <p
>It can be used like this to look up a given MIME type:
</p
>
9783 % ./apt-find-browserplug-for-mimetype
9784 Browser plugin packages supporting audio/ogg:
9786 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
9787 Browser plugin packages supporting application/x-shockwave-flash:
9788 browser-plugin-gnash
9792 <p
>In Ubuntu this mechanism is combined with support in the browser
9793 itself to query for plugins and propose to install the needed
9794 packages. It would be great if Debian supported such feature too. Is
9795 anyone working on adding it?
</p
>
9797 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
9798 request for icweasel support for this feature is
9799 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
9800 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
9801 of manpower and wish for a different design is the reason thus feature
9802 is not yet in iceweasel from Debian.
</p
>
9807 <title>What is the most supported MIME type in Debian?
</title>
9808 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
9809 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
9810 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
9811 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
9812 proposal to add AppStream information to the Debian archive
</a
>, is a
9813 proposal to make it possible for a Desktop application to propose to
9814 the user some package to install to gain support for a given MIME
9815 type, font, library etc. that is currently missing. With such
9816 mechanism in place, it would be possible for the desktop to
9817 automatically propose and install leocad if some LDraw file is
9818 downloaded by the browser.
</p
>
9820 <p
>To get some idea about the current content of the archive, I decided
9821 to write a simple program to extract all .desktop files from the
9822 Debian archive and look up the claimed MIME support there. The result
9824 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
9825 site
</a
>. Using the collected information, it become possible to
9826 answer the question in the title. Here are the
20 most supported MIME
9827 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
9828 The complete list is available from the link above.
</p
>
9830 <p
><strong
>Debian Stable:
</strong
></p
>
9834 ----- -----------------------
9850 18 application/x-ogg
9857 <p
><strong
>Debian Testing:
</strong
></p
>
9861 ----- -----------------------
9877 18 application/x-ogg
9884 <p
><strong
>Debian Unstable:
</strong
></p
>
9888 ----- -----------------------
9905 18 application/x-ogg
9911 <p
>I am told that PackageKit can provide an API to access the kind of
9912 information mentioned in DEP-
11. I have not yet had time to look at
9913 it, but hope the PackageKit people in Debian are on top of these
9916 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
9917 discovering a typo in my script.
</p
>
9922 <title>Using modalias info to find packages handling my hardware
</title>
9923 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
9924 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
9925 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
9926 <description><p
>Yesterday, I wrote about the
9927 <a href=
"https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
9928 values provided by the Linux kernel
</a
> following my hope for
9929 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
9930 dongle support in Debian
</a
>. Using this knowledge, I have tested how
9931 modalias values attached to package names can be used to map packages
9932 to hardware. This allow the system to look up and suggest relevant
9933 packages when I plug in some new hardware into my machine, and replace
9934 discover and discover-data as the database used to map hardware to
9937 <p
>I create a modaliases file with entries like the following,
9938 containing package name, kernel module name (if relevant, otherwise
9939 the package name) and globs matching the relevant hardware
9942 <p
><blockquote
>
9943 Package: package-name
9944 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
9945 </blockquote
></p
>
9947 <p
>It is fairly trivial to write code to find the relevant packages
9948 for a given modalias value using this file.
</p
>
9950 <p
>An entry like this would suggest the video and picture application
9951 cheese for many USB web cameras (interface bus class
0E01):
</p
>
9953 <p
><blockquote
>
9955 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
9956 </blockquote
></p
>
9958 <p
>An entry like this would suggest the pcmciautils package when a
9959 CardBus bridge (bus class
0607) PCI device is present:
</p
>
9961 <p
><blockquote
>
9962 Package: pcmciautils
9963 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
9964 </blockquote
></p
>
9966 <p
>An entry like this would suggest the package colorhug-client when
9967 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
9969 <p
><blockquote
>
9970 Package: colorhug-client
9971 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
9972 </blockquote
></p
>
9974 <p
>I believe the format is compatible with the format of the Packages
9975 file in the Debian archive. Ubuntu already uses their Packages file
9976 to store their mappings from packages to hardware.
</p
>
9978 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
9979 announce the hardware it support in a way my prototype understand.
9980 This allow those publishing packages in an APT source outside the
9981 Debian archive as well as those backporting packages to make sure the
9982 hardware mapping are included in the package meta information. I
've
9983 tested such header in the pymissile package, and its modalias mapping
9984 is working as it should with my prototype. It even made it to Ubuntu
9987 <p
>To test if it was possible to look up supported hardware using only
9988 the shell tools available in the Debian installer, I wrote a shell
9989 implementation of the lookup code. The idea is to create files for
9990 each modalias and let the shell do the matching. Please check out and
9992 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
9993 shell script. It run without any extra dependencies and fetch the
9994 hardware mappings from the Debian archive and the subversion
9995 repository where I currently work on my prototype.
</p
>
9997 <p
>When I use it on a machine with a yubikey inserted, it suggest to
9998 install yubikey-personalization:
</p
>
10000 <p
><blockquote
>
10001 % ./hw-support-lookup
10002 <br
>yubikey-personalization
10004 </blockquote
></p
>
10006 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
10007 propose to install the pcmciautils package:
</p
>
10009 <p
><blockquote
>
10010 % ./hw-support-lookup
10011 <br
>pcmciautils
10013 </blockquote
></p
>
10015 <p
>If you know of any hardware-package mapping that should be added to
10016 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
10017 database
</a
>, please tell me about it.
</p
>
10019 <p
>It could be possible to generate several of the mappings between
10020 packages and hardware. One source would be to look at packages with
10021 kernel modules, ie packages with *.ko files in /lib/modules/, and
10022 extract their modalias information. Another would be to look at
10023 packages with udev rules, ie packages with files in
10024 /lib/udev/rules.d/, and extract their vendor/model information to
10025 generate a modalias matching rule. I have not tested any of these to
10026 see if it work.
</p
>
10028 <p
>If you want to help implementing a system to let us propose what
10029 packages to install when new hardware is plugged into a Debian
10030 machine, please send me an email or talk to me on
10031 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
10036 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
10037 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
10038 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
10039 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
10040 <description><p
>While looking into how to look up Debian packages based on hardware
10041 information, to find the packages that support a given piece of
10042 hardware, I refreshed my memory regarding modalias values, and decided
10043 to document the details. Here are my findings so far, also available
10045 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
10046 Debian Edu subversion repository
</a
>:
10048 <p
><strong
>Modalias decoded
</strong
></p
>
10050 <p
>This document try to explain what the different types of modalias
10051 values stands for. It is in part based on information from
10052 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
10053 &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;,
10054 &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
10055 &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;.
10057 <p
>The modalias entries for a given Linux machine can be found using
10058 this shell script:
</p
>
10061 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
10064 <p
>The supported modalias globs for a given kernel module can be found
10065 using modinfo:
</p
>
10068 % /sbin/modinfo psmouse | grep alias:
10069 alias: serio:ty05pr*id*ex*
10070 alias: serio:ty01pr*id*ex*
10074 <p
><strong
>PCI subtype
</strong
></p
>
10076 <p
>A typical PCI entry can look like this. This is an Intel Host
10077 Bridge memory controller:
</p
>
10079 <p
><blockquote
>
10080 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
10081 </blockquote
></p
>
10083 <p
>This represent these values:
</p
>
10086 v
00008086 (vendor)
10087 d
00002770 (device)
10088 sv
00001028 (subvendor)
10089 sd
000001AD (subdevice)
10091 sc
00 (bus subclass)
10095 <p
>The vendor/device values are the same values outputted from
'lspci
10096 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
10097 0600. The
0600 class is a host bridge. Other useful bus values are
10098 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
10100 <p
>Not sure how to figure out the interface value, nor what it
10103 <p
><strong
>USB subtype
</strong
></p
>
10105 <p
>Some typical USB entries can look like this. This is an internal
10106 USB hub in a laptop:
</p
>
10108 <p
><blockquote
>
10109 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
10110 </blockquote
></p
>
10112 <p
>Here is the values included in this alias:
</p
>
10115 v
1D6B (device vendor)
10116 p
0001 (device product)
10118 dc
09 (device class)
10119 dsc
00 (device subclass)
10120 dp
00 (device protocol)
10121 ic
09 (interface class)
10122 isc
00 (interface subclass)
10123 ip
00 (interface protocol)
10126 <p
>The
0900 device class/subclass means hub. Some times the relevant
10127 class is in the interface class section. For a simple USB web camera,
10128 these alias entries show up:
</p
>
10130 <p
><blockquote
>
10131 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
10132 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
10133 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
10134 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
10135 </blockquote
></p
>
10137 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
10138 camera),
0101 is audio control device and
0102 is audio streaming (aka
10139 microphone). Thus this is a camera with microphone included.
</p
>
10141 <p
><strong
>ACPI subtype
</strong
></p
>
10143 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
10144 receiver in a Thinkpad X40:
</p
>
10146 <p
><blockquote
>
10147 acpi:IBM0071:PNP0511:
10148 </blockquote
></p
>
10150 <p
>The values between the colons are IDs.
</p
>
10152 <p
><strong
>DMI subtype
</strong
></p
>
10154 <p
>The DMI table contain lots of information about the computer case
10155 and model. This is an entry for a IBM Thinkpad X40, fetched from
10156 /sys/devices/virtual/dmi/id/modalias:
</p
>
10158 <p
><blockquote
>
10159 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
10160 </blockquote
></p
>
10162 <p
>The values present are
</p
>
10165 bvn IBM (BIOS vendor)
10166 bvr
1UETB
6WW(
1.66) (BIOS version)
10167 bd
06/
15/
2005 (BIOS date)
10168 svn IBM (system vendor)
10169 pn
2371H4G (product name)
10170 pvr ThinkPadX40 (product version)
10171 rvn IBM (board vendor)
10172 rn
2371H4G (board name)
10173 rvr NotAvailable (board version)
10174 cvn IBM (chassis vendor)
10175 ct
10 (chassis type)
10176 cvr NotAvailable (chassis version)
10179 <p
>The chassis type
10 is Notebook. Other interesting values can be
10180 found in the dmidecode source:
</p
>
10184 4 Low Profile Desktop
10197 17 Main Server Chassis
10198 18 Expansion Chassis
10200 20 Bus Expansion Chassis
10201 21 Peripheral Chassis
10203 23 Rack Mount Chassis
10212 <p
>The chassis type values are not always accurately set in the DMI
10213 table. For example my home server is a tower, but the DMI modalias
10214 claim it is a desktop.
</p
>
10216 <p
><strong
>SerIO subtype
</strong
></p
>
10218 <p
>This type is used for PS/
2 mouse plugs. One example is from my
10219 test machine:
</p
>
10221 <p
><blockquote
>
10222 serio:ty01pr00id00ex00
10223 </blockquote
></p
>
10225 <p
>The values present are
</p
>
10234 <p
>This type is supported by the psmouse driver. I am not sure what
10235 the valid values are.
</p
>
10237 <p
><strong
>Other subtypes
</strong
></p
>
10239 <p
>There are heaps of other modalias subtypes according to
10240 file2alias.c. There is the rest of the list from that source: amba,
10241 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
10242 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
10243 vmbus, x86cpu and zorro. I did not spend time documenting all of
10244 these, as they do not seem relevant for my intended use with mapping
10245 hardware to packages when new stuff is inserted during run time.
</p
>
10247 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
10249 <p
>To check which kernel modules provide support for a given modalias,
10250 one can use the following shell script:
</p
>
10253 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
10254 echo
"$id
" ; \
10255 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
10259 <p
>The output can look like this (only the first few entries as the
10260 list is very long on my test machine):
</p
>
10264 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
10266 FATAL: Module acpi:device: not found.
10268 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
10269 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
10270 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
10271 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
10272 acpi:IBM0071:PNP0511:
10273 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
10274 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
10275 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
10279 <p
>If you want to help implementing a system to let us propose what
10280 packages to install when new hardware is plugged into a Debian
10281 machine, please send me an email or talk to me on
10282 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
10284 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
10285 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
10286 in /sys/ with space in them.
</p
>
10291 <title>Moved the pymissile Debian packaging to collab-maint
</title>
10292 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
10293 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
10294 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
10295 <description><p
>As part of my investigation on how to improve the support in Debian
10296 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
10297 Launcher and updated the Debian package
10298 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
10299 sure udev will fix the device permissions when it is plugged in. I
10300 also added a
"Modaliases
" header to test it in the Debian archive and
10301 hopefully make the package be proposed by jockey in Ubuntu when a user
10302 plug in his rocket launcher. In the process I moved the source to a
10303 git repository under collab-maint, to make it easier for any DD to
10304 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
10305 is not very active, but the software still work for me even after five
10306 years of relative silence. The new git repository is not listed in
10307 the uploaded package yet, because I want to test the other changes a
10308 bit more before I upload the new version. If you want to check out
10309 the new version with a .desktop file included, visit the
10310 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
10311 view
</a
> or use
"<tt
>git clone
10312 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
10317 <title>Lets make hardware dongles easier to use in Debian
</title>
10318 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
10319 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
10320 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
10321 <description><p
>One thing that annoys me with Debian and Linux distributions in
10322 general, is that there is a great package management system with the
10323 ability to automatically install software packages by downloading them
10324 from the distribution mirrors, but no way to get it to automatically
10325 install the packages I need to use the hardware I plug into my
10326 machine. Even if the package to use it is easily available from the
10327 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
10328 suggest to automatically install the python-nxt, nbc and t2n packages
10329 I need to talk to it. When I plug in a Yubikey, it could propose the
10330 yubikey-personalization package. The information required to do this
10331 is available, but no-one have pulled all the pieces together.
</p
>
10333 <p
>Some years ago, I proposed to
10334 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
10335 the discover subsystem to implement this
</a
>. The idea is fairly
10340 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
10341 starting when a user log in.
</li
>
10343 <li
>Set this program up to listen for kernel events emitted when new
10344 hardware is inserted into the computer.
</li
>
10346 <li
>When new hardware is inserted, look up the hardware ID in a
10347 database mapping to packages, and take note of any non-installed
10348 packages.
</li
>
10350 <li
>Show a message to the user proposing to install the discovered
10351 package, and make it easy to install it.
</li
>
10355 <p
>I am not sure what the best way to implement this is, but my
10356 initial idea was to use dbus events to discover new hardware, the
10357 discover database to find packages and
10358 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
10359 packages.
</p
>
10361 <p
>Yesterday, I found time to try to implement this idea, and the
10362 draft package is now checked into
10363 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
10364 Debian Edu subversion repository
</a
>. In the process, I updated the
10365 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
10366 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
10367 the relevant packages in Debian, and uploaded a new version
10368 2.2013.01.09 to unstable. I also discovered that the current
10369 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
10370 package in Debian no longer discovered any USB devices, because
10371 /proc/bus/usb/devices is no longer present. I ported it to use
10372 libusb as a fall back option to get it working. The fixed package
10373 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
10374 because of the freeze).
</p
>
10376 <p
>With this prototype in place, I can insert my Yubikey, and get this
10377 desktop notification to show up (only once, the first time it is
10378 inserted):
</p
>
10380 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
10382 <p
>For this prototype to be really useful, some way to automatically
10383 install the proposed packages by pressing the
"Please install
10384 program(s)
" button should to be implemented.
</p
>
10386 <p
>If this idea seem useful to you, and you want to help make it
10387 happen, please help me update the discover-data database with mappings
10388 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
10389 list the package you would like to have installed when a given
10390 hardware device is inserted into your computer, and report bugs using
10391 reportbug if it isn
't. Or, if you know of a better way to provide
10392 such mapping, please let me know.
</p
>
10394 <p
>This prototype need more work, and there are several questions that
10395 should be considered before it is ready for production use. Is dbus
10396 the correct way to detect new hardware? At the moment I look for HAL
10397 dbus events on the system bus, because that is the events I could see
10398 on my Debian Squeeze KDE desktop. Are there better events to use?
10399 How should the user be notified? Is the desktop notification
10400 mechanism the best option, or should the background daemon raise a
10401 popup instead? How should packages be installed? When should they
10402 not be installed?
</p
>
10404 <p
>If you want to help getting such feature implemented in Debian,
10405 please send me an email. :)
</p
>
10410 <title>New IRC channel for LEGO designers using Debian
</title>
10411 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
10412 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
10413 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
10414 <description><p
>During Christmas, I have worked a bit on the Debian support for
10415 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
10416 NXT
</a
>. My son and I have played a bit with my NXT set, and I
10417 discovered I had to build all the tools myself because none were
10418 already in Debian Squeeze. If Debian support for LEGO is something
10419 you care about, please join me on the IRC channel
10420 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
10421 irc.debian.org). There is a lot that could be done to improve the
10422 Debian support for LEGO designers. For example both CAD software
10423 and Mindstorm compilers are missing. :)
</p
>
10425 <p
>Update
2012-
01-
03: A
10426 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
10427 including links to Lego related packages is now available.
</p
>
10432 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
10433 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
10434 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
10435 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
10436 <description><p
>Let me start by wishing you all marry Christmas and a happy new
10437 year! I hope next year will prove to be a good year.
</p
>
10439 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
10440 decentralised
"currency
" that allow people to transfer bitcoins
10441 between each other with minimal overhead, is a very interesting
10442 experiment. And as I wrote a few days ago, the bitcoin situation in
10443 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
10444 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
10445 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
10446 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
10447 for one of the ftpmasters to approve the new bitcoin-qt package
10450 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
10451 team in Debian, you can easily test the package in Debian Squeeze
10452 using the following steps to get a set of working packages:
</p
>
10454 <blockquote
><pre
>
10455 git clone git://git.debian.org/git/collab-maint/bitcoin
10457 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
10458 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
10459 </pre
></blockquote
>
10461 <p
>You might have to install some build dependencies as well. The
10462 list of commands should give you two packages, bitcoind and
10463 bitcoin-qt, ready for use in a Squeeze environment. Note that the
10464 client will download the complete set of bitcoin
"blocks
", which need
10465 around
5.6 GiB of data on my machine at the moment. Make sure your
10466 ~/.bitcoin/ directory have lots of spare room if you want to download
10467 all the blocks. The client will warn if the disk is getting full, so
10468 there is not really a problem if you got too little room, but you will
10469 not be able to get all the features out of the client.
</p
>
10471 <p
>As usual, if you use bitcoin and want to show your support of my
10472 activities, please send Bitcoin donations to my address
10473 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
10478 <title>A word on bitcoin support in Debian
</title>
10479 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
10480 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
10481 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
10482 <description><p
>It has been a while since I wrote about
10483 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
10484 peer-to-peer based crypto-currency, and the reason is simply that I
10485 have been busy elsewhere. But two days ago, I started looking at the
10486 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
10487 Debian
</a
> again to try to recover my old bitcoin wallet. The package
10488 is now maintained by a
10489 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
10490 people
</a
>, and the grunt work had already been done by this team. We
10491 owe a huge thank you to all these team members. :)
10492 But I was sad to discover that the bitcoin client is missing in
10493 Wheezy. It is only available in Sid (and an outdated client from
10494 backports). The client had several RC bugs registered in BTS blocking
10495 it from entering testing. To try to help the team and improve the
10496 situation, I spent some time providing patches and triaging the bug
10497 reports. I also had a look at the bitcoin package available from Matt
10499 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
10500 Ubuntu
</a
>, and moved the useful pieces from that version into the
10501 Debian package.
</p
>
10503 <p
>After checking with the main package maintainer Jonas Smedegaard on
10504 IRC, I pushed several patches into the collab-maint git repository to
10505 improve the package. It now contains fixes for the RC issues (not from
10506 me, but fixed by Scott Howard), build rules for a Qt GUI client
10507 package, konqueror support for the bitcoin: URI and bash completion
10508 setup. As I work on Debian Squeeze, I also created
10509 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
10510 patch to backport
</a
> the latest version. Jonas is going to look at
10511 it and try to integrate it into the git repository before uploading a
10512 new version to unstable.
10514 <p
>I would very much like bitcoin to succeed, to get rid of the
10515 centralized control currently exercised in the monetary system. I
10516 find it completely unacceptable that the USA government is collecting
10517 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
10518 that the major credit card companies can block legal money
10519 transactions to Wikileaks. But for bitcoin to succeed, more people
10520 need to use bitcoins, and more people need to accept bitcoins when
10521 they sell products and services. Improving the bitcoin support in
10522 Debian is a small step in the right direction, but not enough.
10523 Unfortunately the user experience when browsing the web and wanting to
10524 pay with bitcoin is still not very good. The bitcoin: URI is a step
10525 in the right direction, but need to work in most or every browser in
10526 use. Also the bitcoin-qt client is too heavy to fire up to do a
10527 quick transaction. I believe there are other clients available, but
10528 have not tested them.
</p
>
10531 <a href=
"https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
10532 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
10533 I received
20.15 BTC so far on the address I provided in my blog two
10534 years ago, as can be
10535 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
10536 on the blockexplorer service
</a
>. Thank you everyone for your
10537 donation. The blockexplorer service demonstrates quite well that
10538 bitcoin is not quite anonymous and untracked. :) I wonder if the
10539 number of users have gone up since then. If you use bitcoin and want
10540 to show your support of my activity, please send Bitcoin donations to
10541 the same address as last time,
10542 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
10547 <title>Git repository for song book for Computer Scientists
</title>
10548 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
10549 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
10550 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
10551 <description><p
>As I
10552 <a href=
"https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
10553 this summer
</a
>, I have created a Computer Science song book a few
10554 years ago, and today I finally found time to create a public
10555 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
10556 repository for the project
</a
>.
</p
>
10558 <p
>If you want to help out, please clone the source and submit patches
10559 to the HTML version. To generate the PDF and PostScript version,
10560 please use prince XML, or let me know about a useful free software
10561 processor capable of creating a good looking PDF from the HTML.
</p
>
10563 <p
>Want to sing? You can still find the song book in HTML, PDF and
10564 PostScript formats at
10565 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
10566 Science Songbook
</a
>.
</p
>
10571 <title>Gratulerer med
19-årsdagen, Debian!
</title>
10572 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
10573 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
10574 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
10575 <description><p
>I dag fyller
10576 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
10577 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
10578 si gratulerer med dagen, Debian!
</p
>
10583 <title>Song book for Computer Scientists
</title>
10584 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
10585 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
10586 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
10587 <description><p
>Many years ago, while studying Computer Science at the
10588 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
10589 collecting computer related songs for use at parties. The original
10590 version was written in LaTeX, but a few years ago I got help from
10591 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
10592 while keeping the ability to create a nice book in PDF format. I have
10593 not had time to maintain the book for a while now, and guess I should
10594 put it up on some public version control repository where others can
10595 help me extend and update the book. If anyone is volunteering to help
10596 me with this, send me an email. Also let me know if there are songs
10597 missing in my book.
</p
>
10599 <p
>I have not mentioned the book on my blog so far, and it occured to
10600 me today that I really should let all my readers share the joys of
10601 singing out load about programming, computers and computer networks.
10602 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
10603 12</a
> is about to start (and I am not going). Want to sing? Check
10604 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
10605 Computer Science Songbook
</a
>.
10610 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
10611 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
10612 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
10613 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
10614 <description><p
>At work we have heaps of servers. I believe the total count is
10615 around
1000 at the moment. To be able to get help from the vendors
10616 when something go wrong, we want to keep the firmware on the servers
10617 up to date. If the firmware isn
't the latest and greatest, the
10618 vendors typically refuse to start debugging any problems until the
10619 firmware is upgraded. So before every reboot, we want to upgrade the
10620 firmware, and we would really like everyone handling servers at the
10621 university to do this themselves when they plan to reboot a machine.
10622 For that to happen we at the unix server admin group need to provide
10623 the tools to do so.
</p
>
10625 <p
>To make firmware upgrading easier, I am working on a script to
10626 fetch and install the latest firmware for the servers we got. Most of
10627 our hardware are from Dell and HP, so I have focused on these servers
10628 so far. This blog post is about the Dell part.
</P
>
10630 <p
>On the Dell FTP site I was lucky enough to find
10631 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
10632 with firmware information for all
11th generation servers, listing
10633 which firmware should be used on a given model and where on the FTP
10634 site I can find it. Using a simple perl XML parser I can then
10635 download the shell scripts Dell provides to do firmware upgrades from
10636 within Linux and reboot when all the firmware is primed and ready to
10637 be activated on the first reboot.
</p
>
10639 <p
>This is the Dell related fragment of the perl code I am working on.
10640 Are there anyone working on similar tools for firmware upgrading all
10641 servers at a site? Please get in touch and lets share resources.
</p
>
10643 <p
><pre
>
10647 use File::Temp qw(tempdir);
10649 # Install needed RHEL packages if missing
10650 my %rhelmodules = (
10651 'XML::Simple
' =
> 'perl-XML-Simple
',
10653 for my $module (keys %rhelmodules) {
10654 eval
"use $module;
";
10656 my $pkg = $rhelmodules{$module};
10657 system(
"yum install -y $pkg
");
10658 eval
"use $module;
";
10662 my $errorsto =
'pere@hungry.com
';
10668 sub run_firmware_script {
10669 my ($opts, $script) = @_;
10671 print STDERR
"fail: missing script name\n
";
10674 print STDERR
"Running $script\n\n
";
10676 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
10677 print STDERR
"success: firmware script ran succcessfully\n
";
10679 print STDERR
"fail: firmware script returned error\n
";
10683 sub run_firmware_scripts {
10684 my ($opts, @dirs) = @_;
10685 # Run firmware packages
10686 for my $dir (@dirs) {
10687 print STDERR
"info: Running scripts in $dir\n
";
10688 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
10689 while (my $s = readdir $dh) {
10690 next if $s =~ m/^\.\.?/;
10691 run_firmware_script($opts,
"$dir/$s
");
10699 print STDERR
"info: Downloading $url\n
";
10700 system(
"wget --quiet \
"$url\
"");
10705 my $product = `dmidecode -s system-product-name`;
10708 if ($product =~ m/PowerEdge/) {
10710 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
10711 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
10713 my $tmpdir = tempdir(
10717 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
10718 system(
'gunzip Catalog.xml.gz
');
10719 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
10720 # -q is quiet, disabling interactivity and reducing console output
10721 my $fwopts =
"-q
";
10723 for my $url (@paths) {
10724 fetch_dell_fw($url);
10726 run_firmware_scripts($fwopts, $tmpdir);
10728 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
10729 print STDERR
"error: Please report to $errorsto.\n
";
10731 chdir(
'/
');
10733 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
10734 print STDERR
"error: Please report to $errorsto.\n
";
10738 sub fetch_dell_fw {
10740 my $url =
"ftp://ftp.us.dell.com/$path
";
10744 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
10745 # firmware packages to download from Dell. Only work for Linux
10746 # machines and
11th generation Dell servers.
10747 sub fetch_dell_fw_list {
10748 my $filename = shift;
10750 my $product = `dmidecode -s system-product-name`;
10752 my ($mybrand, $mymodel) = split(/\s+/, $product);
10754 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
10756 my $xml = XMLin($filename);
10758 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
10759 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
10760 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
10762 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
10763 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
10765 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
10767 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
10769 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
10772 for my $component (@{$xml-
>{SoftwareComponent}}) {
10773 my $componenttype = $component-
>{ComponentType}-
>{value};
10775 # Drop application packages, only firmware and BIOS
10776 next if
'APAC
' eq $componenttype;
10778 my $cpath = $component-
>{path};
10779 for my $path (@paths) {
10780 if ($cpath =~ m%/$path$%) {
10781 push(@paths, $cpath);
10789 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
10790 it could work on other platforms with some tweaking. Anyone know a
10791 index like Catalog.xml is available from HP for HP servers? At the
10792 moment I maintain a similar list manually and it is quickly getting
10793 outdated.
</p
>
10798 <title>How is booting into runlevel
1 different from single user boots?
</title>
10799 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
10800 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
10801 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
10802 <description><p
>Wouter Verhelst have some
10803 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
10804 comments and opinions
</a
> on my blog post on
10805 <a href=
"https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
10806 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
10807 <a href=
"https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
10808 default KDE desktop in Debian
</a
>. I only have time to address one
10809 small piece of his comment now, and though it best to address the
10810 misunderstanding he bring forward:
</p
>
10812 <p
><blockquote
>
10813 Currently, a system admin has four options: [...] boot to a
10814 single-user system (by adding
'single
' to the kernel command line;
10815 this runs rcS and rc1 scripts)
10816 </blockquote
></p
>
10818 <p
>This make me believe Wouter believe booting into single user mode
10819 and booting into runlevel
1 is the same. I am not surprised he
10820 believe this, because it would make sense and is a quite sensible
10821 thing to believe. But because the boot in Debian is slightly broken,
10822 runlevel
1 do not work properly and it isn
't the same as single user
10823 mode. I
'll try to explain what is actually happing, but it is a bit
10824 hard to explain.
</p
>
10826 <p
>Single user mode is defined like this in /etc/inittab:
10827 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
10828 executed in single user mode is sulogin. Single user mode is a boot
10829 state
"between
" the runlevels, and when booting into single user mode,
10830 only the scripts in /etc/rcS.d/ are executed before the init process
10831 enters the single user state. When switching to runlevel
1, the state
10832 is in fact not ending in runlevel
1, but it passes through runlevel
1
10833 and end up in the single user mode (see /etc/rc1.d/S03single, which
10834 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
10835 1. It is confusing that the
'S
' (single user) init mode is not the
10836 mode enabled by /etc/rcS.d/ (which is more like the initial boot
10839 <p
>This summary might make it clearer. When booting for the first
10840 time into single user mode, the following commands are executed:
10841 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
10842 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
10843 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
10844 trying to continue after visiting single user mode. Not all services
10845 are started again as they should, causing the machine to end up in an
10846 unpredicatble state. This is why Debian admins recommend rebooting
10847 after visiting single user mode.
</p
>
10849 <p
>A similar problem with runlevel
1 is caused by the amount of
10850 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
10851 to runlevel
1, the services started from /etc/rcS.d/ are not properly
10852 stopped when passing through the scripts in /etc/rc1.d/, and not
10853 started again when switching away from runlevel
1 to the runlevels
10854 2-
5. I believe the problem is best fixed by moving all the scripts
10855 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
10856 functioning single user mode during boot.
</p
>
10858 <p
>I have spent several years investigating the Debian boot system,
10859 and discovered this problem a few years ago. I suspect it originates
10860 from when sysvinit was introduced into Debian, a long time ago.
</p
>
10865 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
10866 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
10867 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
10868 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
10869 <description><p
>In the Debian boot system, several packages include scripts that
10870 are started from /etc/rcS.d/. In fact, there is a bite more of them
10871 than make sense, and this causes a few problems. What kind of
10872 problems, you might ask. There are at least two problems. The first
10873 is that it is not possible to recover a machine after switching to
10874 runlevel
1. One need to actually reboot to get the machine back to
10875 the expected state. The other is that single user boot will sometimes
10876 run into problems because some of the subsystems are activated before
10877 the root login is presented, causing problems when trying to recover a
10878 machine from a problem in that subsystem. A minor additional point is
10879 that moving more scripts out of rcS.d/ and into the other rc#.d/
10880 directories will increase the amount of scripts that can run in
10881 parallel during boot, and thus decrease the boot time.
</p
>
10883 <p
>So, which scripts should start from rcS.d/. In short, only the
10884 scripts that _have_ to execute before the root login prompt is
10885 presented during a single user boot should go there. Everything else
10886 should go into the numeric runlevels. This means things like
10887 lm-sensors, fuse and x11-common should not run from rcS.d, but from
10888 the numeric runlevels. Today in Debian, there are around
115 init.d
10889 scripts that are started from rcS.d/, and most of them should be moved
10890 out. Do your package have one of them? Please help us make single
10891 user and runlevel
1 better by moving it.
</p
>
10893 <p
>Scripts setting up the screen, keyboard, system partitions
10894 etc. should still be started from rcS.d/, but there is for example no
10895 need to have the network enabled before the single user login prompt
10896 is presented.
</p
>
10898 <p
>As always, things are not so easy to fix as they sound. To keep
10899 Debian systems working while scripts migrate and during upgrades, the
10900 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
10901 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
10902 and the next ones can only be moved when their dependencies have been
10903 moved first. This migration must be done sequentially while we ensure
10904 that the package system upgrade packages in the right order to keep
10905 the system state correct. This will require some coordination when it
10906 comes to network related packages, but most of the packages with
10907 scripts that should migrate do not have anything in rcS.d/ depending
10908 on them. Some packages have already been updated, like the sudo
10909 package, while others are still left to do. I wish I had time to work
10910 on this myself, but real live constrains make it unlikely that I will
10911 find time to push this forward.
</p
>
10916 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
10917 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
10918 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
10919 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
10920 <description><p
>While at Debconf11, I have several times during discussions
10921 mentioned the issues I believe should be improved in Debian for its
10922 desktop to be useful for more people. The use case for this is my
10923 parents, which are currently running Kubuntu which solve the
10926 <p
>I suspect these four missing features are not very hard to
10927 implement. After all, they are present in Ubuntu, so if we wanted to
10928 do this in Debian we would have a source.
</p
>
10932 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
10933 are new packages available for upgrades, a icon in the KDE status bar
10934 indicate this, and clicking on it will activate the simple upgrade
10935 tool to handle it. I have no problem guiding both of my parents
10936 through the process over the phone. If a kernel reboot is required,
10937 this too is indicated by the status bars and the upgrade tool. Last
10938 time I checked, nothing with the same features was working in KDE in
10941 <li
><strong
>Simple handling of missing Firefox browser
10942 plugins.
</strong
> When the browser encounter a MIME type it do not
10943 currently have a handler for, it will ask the user if the system
10944 should search for a package that would add support for this MIME type,
10945 and if the user say yes, the APT sources will be searched for packages
10946 advertising the MIME type in their control file (visible in the
10947 Packages file in the APT archive). If one or more packages are found,
10948 it is a simple click of the mouse to add support for the missing mime
10949 type. If the package require the user to accept some non-free
10950 license, this is explained to the user. The entire process make it
10951 more clear to the user why something do not work in the browser, and
10952 make the chances higher for the user to blame the web page authors and
10953 not the browser for any missing features.
</li
>
10955 <li
><strong
>Simple handling of missing multimedia codec/format
10956 handlers.
</strong
> When the media players encounter a format or codec
10957 it is not supporting, a dialog pop up asking the user if the system
10958 should search for a package that would add support for it. This
10959 happen with things like MP3, Windows Media or H
.264. The selection
10960 and installation procedure is very similar to the Firefox browser
10961 plugin handling. This is as far as I know implemented using a
10962 gstreamer hook. The end result is that the user easily get access to
10963 the codecs that are present from the APT archives available, while
10964 explaining more on why a given format is unsupported by Ubuntu.
</li
>
10966 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
10967 displaying a text/plain file in my Debian browser, it will propose to
10968 start emacs to show it. If I remember correctly, when doing the same
10969 in Kunbutu it show the file as a text file in the browser. At least I
10970 know Opera will show text files within the browser. I much prefer the
10971 latter behaviour.
</li
>
10975 <p
>There are other nice features as well, like the simplified suite
10976 upgrader, but given that I am the one mostly doing the dist-upgrade,
10977 it do not matter much.
</p
>
10979 <p
>I really hope we could get these features in place for the next
10980 Debian release. It would require the coordinated effort of several
10981 maintainers, but would make the end user experience a lot better.
</p
>
10986 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
10987 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
10988 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
10989 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
10990 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
10991 site is build on Debian/Squeeze, and this platform was chosen because
10992 I am most familiar with Debian (being a Debian Developer for around
10
10993 years) because it is the latest stable Debian release which should get
10994 security support for a few years.
</p
>
10996 <p
>The web service is written in Perl, and depend on some perl modules
10997 that are missing in Debian at the moment. It would be great if these
10998 modules were added to the Debian archive, allowing anyone to set up
10999 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
11000 in their own country using only Debian packages. The list of modules
11001 missing in Debian/Squeeze isn
't very long, and I hope the perl group
11002 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
11003 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
11004 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
11005 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
11006 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
11007 easier in the future.
</p
>
11009 <p
>Thanks to the great tools in Debian, getting the missing modules
11010 installed on my server was a simple call to
'cpan2deb Module::Name
'
11011 and
'dpkg -i
' to install the resulting package. But this leave me
11012 with the responsibility of tracking security problems, which I really
11013 do not have time for.
</p
>
11018 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
11019 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
11020 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
11021 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
11022 <description><p
>Here is a small update for my English readers. Most of my blog
11023 posts have been in Norwegian the last few weeks, so here is a short
11024 update in English.
</p
>
11026 <p
>The kids still keep me too busy to get much free software work
11027 done, but I did manage to organise a project to get a Norwegian port
11028 of the British service
11029 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
11030 and it has been running for a month now. The entire project has been
11031 organised by me and two others. Around Christmas we gathered sponsors
11032 to fund the development work. In January I drafted a contract with
11033 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
11034 and in February the development took place. Most of it involved
11035 converting the source to use GPS coordinates instead of British
11036 easting/northing, and the resulting code should be a lot easier to get
11037 running in any country by now. The Norwegian
11038 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
11039 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
11040 source and the source for administrative borders in Norway, and
11041 support for this had to be added/fixed.
</p
>
11043 <p
>The Norwegian version went live March
3th, and we spent the weekend
11044 polishing the system before we announced it March
7th. The system is
11045 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
11046 problem reports in a few weeks. Soon we hope to announce the Android
11047 and iPhone versions making it even easier to report problems with the
11048 public infrastructure.
</p
>
11050 <p
>Perhaps something to consider for those of you in countries without
11051 such service?
</p
>
11056 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
11057 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
11058 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
11059 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
11060 <description><p
>The last few days I have looked at ways to track open security
11061 issues here at my work with the University of Oslo. My idea is that
11062 it should be possible to use the information about security issues
11063 available on the Internet, and check our locally
11064 maintained/distributed software against this information. It should
11065 allow us to verify that no known security issues are forgotten. The
11066 CVE database listing vulnerabilities seem like a great central point,
11067 and by using the package lists from Debian mapped to CVEs provided by
11068 the testing security team, I believed it should be possible to figure
11069 out which security holes were present in our free software
11070 collection.
</p
>
11072 <p
>After reading up on the topic, it became obvious that the first
11073 building block is to be able to name software packages in a unique and
11074 consistent way across data sources. I considered several ways to do
11075 this, for example coming up with my own naming scheme like using URLs
11076 to project home pages or URLs to the Freshmeat entries, or using some
11077 existing naming scheme. And it seem like I am not the first one to
11078 come across this problem, as MITRE already proposed and implemented a
11079 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
11080 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
11081 software, hardware and other platform components. The CPE ids are
11082 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
11083 Vulnerability Database
</a
>, allowing me to look up know security
11084 issues for any CPE name. With this in place, all I need to do is to
11085 locate the CPE id for the software packages we use at the university.
11086 This is fairly trivial (I google for
'cve cpe $package
' and check the
11087 NVD entry if a CVE for the package exist).
</p
>
11089 <p
>To give you an example. The GNU gzip source package have the CPE
11090 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
11091 check out, one could look up
11092 <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
11093 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
11094 The most recent one is
11095 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
11096 and at the bottom of the NVD page for this vulnerability the complete
11097 list of affected versions is provided.
</p
>
11099 <p
>The NVD database of CVEs is also available as a XML dump, allowing
11100 for offline processing of issues. Using this dump, I
've written a
11101 small script taking a list of CPEs as input and list all CVEs
11102 affecting the packages represented by these CPEs. One give it CPEs
11103 with version numbers as specified above and get a list of open
11104 security issues out.
</p
>
11106 <p
>Of course for this approach to be useful, the quality of the NVD
11107 information need to be high. For that to happen, I believe as many as
11108 possible need to use and contribute to the NVD database. I notice
11110 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
11111 map from CVE to CPE
</a
>, indicating that they are using the CPE
11112 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
11114 <p
>To get an idea about the quality for free software, I spent some
11115 time making it possible to compare the CVE database from Debian with
11116 the CVE database in NVD. The result look fairly good, but there are
11117 some inconsistencies in NVD (same software package having several
11118 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
11119 Debian believe are affected by a CVE). Hope to find time to improve
11120 the quality of NVD, but that require being able to get in touch with
11121 someone maintaining it. So far my three emails with questions and
11122 corrections have not seen any reply, but I hope contact can be
11123 established soon.
</p
>
11125 <p
>An interesting application for CPEs is cross platform package
11126 mapping. It would be useful to know which packages in for example
11127 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
11128 this would be trivial if all linux distributions provided CPE entries
11129 for their packages.
</p
>
11134 <title>Which module is loaded for a given PCI and USB device?
</title>
11135 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
11136 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
11137 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
11138 <description><p
>In the
11139 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
11140 package in Debian, there is a script to report useful information
11141 about the running hardware for use when people report missing
11142 information. One part of this script that I find very useful when
11143 debugging hardware problems, is the part mapping loaded kernel module
11144 to the PCI device it claims. It allow me to quickly see if the kernel
11145 module I expect is driving the hardware I am struggling with. To see
11146 the output, make sure discover-data is installed and run
11147 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
11148 one of my machines like this:
</p
>
11152 10de:
03eb i2c_nforce2
11155 10de:
03f0 snd_hda_intel
11160 109e:
0878 snd_bt87x
11164 <p
>The code in question look like this, slightly modified for
11165 readability and to drop the output to file descriptor
3:
</p
>
11168 if [ -d /sys/bus/pci/devices/ ] ; then
11169 echo loaded pci modules:
11171 cd /sys/bus/pci/devices/
11172 for address in * ; do
11173 if [ -d
"$address/driver/module
" ] ; then
11174 module=`cd $address/driver/module ; pwd -P | xargs basename`
11175 if grep -q
"^$module
" /proc/modules ; then
11176 address=$(echo $address |sed s/
0000://)
11177 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
11178 echo
"$id $module
"
11187 <p
>Similar code could be used to extract USB device module
11188 mappings:
</p
>
11191 if [ -d /sys/bus/usb/devices/ ] ; then
11192 echo loaded usb modules:
11194 cd /sys/bus/usb/devices/
11195 for address in * ; do
11196 if [ -d
"$address/driver/module
" ] ; then
11197 module=`cd $address/driver/module ; pwd -P | xargs basename`
11198 if grep -q
"^$module
" /proc/modules ; then
11199 address=$(echo $address |sed s/
0000://)
11200 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
11201 if [
"$id
" ] ; then
11202 echo
"$id $module
"
11212 <p
>This might perhaps be something to include in other tools as
11218 <title>How to test if a laptop is working with Linux
</title>
11219 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
11220 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
11221 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
11222 <description><p
>The last few days I have spent at work here at the
<a
11223 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
11224 batch of computers will work with Linux. Every year for the last few
11225 years the university have organised shared bid of a few thousand
11226 computers, and this year HP won the bid. Two different desktops and
11227 five different laptops are on the list this year. We in the UNIX
11228 group want to know which one of these computers work well with RHEL
11229 and Ubuntu, the two Linux distributions we currently handle at the
11230 university.
</p
>
11232 <p
>My test method is simple, and I share it here to get feedback and
11233 perhaps inspire others to test hardware as well. To test, I PXE
11234 install the OS version of choice, and log in as my normal user and run
11235 a few applications and plug in selected pieces of hardware. When
11236 something fail, I make a note about this in the test matrix and move
11237 on. If I have some spare time I try to report the bug to the OS
11238 vendor, but as I only have the machines for a short time, I rarely
11239 have the time to do this for all the problems I find.
</p
>
11241 <p
>Anyway, to get to the point of this post. Here is the simple tests
11242 I perform on a new model.
</p
>
11246 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
11247 and Ubuntu Maverik at the moment. If I feel like it, I also test with
11248 RHEL5 and Debian Edu/Squeeze.
</li
>
11250 <li
>Is X.org working? If the graphical login screen show up after
11251 installation, X.org is working.
</li
>
11253 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
11254 package mesa-utils on Ubuntu) and writing down the frames per second
11255 reported by the program.
</li
>
11257 <li
>Is sound working? With Gnome and KDE, a sound is played when
11258 logging in, and if I can hear this the test is successful. If there
11259 are several audio exits on the machine, I try them all and check if
11260 the Gnome/KDE audio mixer can control where to send the sound. I
11261 normally test this by playing
11262 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
11263 video
</a
> in Firefox/Iceweasel.
</li
>
11265 <li
>Is the USB subsystem working? I test this by plugging in a USB
11266 memory stick and see if Gnome/KDE notices this.
</li
>
11268 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
11269 I have lying around, and see if Gnome/KDE notices this.
</li
>
11271 <li
>Is any built in camera working? Test using cheese, and see if a
11272 picture from the v4l device show up.
</li
>
11274 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
11275 any bluetooth devices are discovered. In my office, I normally see a
11278 <li
>For laptops, is the SD or Compaq Flash reader working. I have
11279 memory modules lying around, and stick them in and see if Gnome/KDE
11280 notice this.
</li
>
11282 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
11283 special button work, and if the laptop continue to work after
11286 <li
>For laptops, is the extra buttons working, like audio level,
11287 adjusting background light, switching on/off external video output,
11288 switching on/off wifi, bluetooth, etc? The set of buttons differ from
11289 laptop to laptop, so I just write down which are working and which are
11292 <li
>Some laptops have smart card readers, finger print readers,
11293 acceleration sensors etc. I rarely test these, as I do not know how
11294 to quickly test if they are working or not, so I only document their
11295 existence.
</li
>
11299 <p
>By now I suspect you are really curious what the test results are
11300 for the HP machines I am testing. I
'm not done yet, so I will report
11301 the test results later. For now I can report that HP
8100 Elite work
11302 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
11303 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
11304 can see, I have most machines left to test. One interesting
11305 observation is that Ubuntu Lucid has almost twice the frame rate than
11306 RHEL6 with glxgears. No idea why.
</p
>
11311 <title>Some thoughts on BitCoins
</title>
11312 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
11313 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
11314 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
11315 <description><p
>As I continue to explore
11316 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
11317 what properties the system have, and how it will be affected by laws
11318 and regulations here in Norway. Here are some random notes.
</p
>
11320 <p
>One interesting thing to note is that since the transactions are
11321 verified using a peer to peer network, all details about a transaction
11322 is known to everyone. This means that if a BitCoin address has been
11323 published like I did with mine in my initial post about BitCoin, it is
11324 possible for everyone to see how many BitCoins have been transfered to
11325 that address. There is even a web service to look at the details for
11326 all transactions. There I can see that my address
11327 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
11328 have received
16.06 Bitcoin, the
11329 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
11330 address of Simon Phipps have received
181.97 BitCoin and the address
11331 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
11332 of EFF have received
2447.38 BitCoins so far. Thank you to each and
11333 every one of you that donated bitcoins to support my activity. The
11334 fact that anyone can see how much money was transfered to a given
11335 address make it more obvious why the BitCoin community recommend to
11336 generate and hand out a new address for each transaction. I
'm told
11337 there is no way to track which addresses belong to a given person or
11338 organisation without the person or organisation revealing it
11339 themselves, as Simon, EFF and I have done.
</p
>
11341 <p
>In Norway, and in most other countries, there are laws and
11342 regulations limiting how much money one can transfer across the border
11343 without declaring it. There are money laundering, tax and accounting
11344 laws and regulations I would expect to apply to the use of BitCoin.
11345 If the Skolelinux foundation
11346 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
11347 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
11348 normal bank transfers like EFF is doing, how should this be accounted?
11349 Given that it is impossible to know if money can cross the border or
11350 not, should everything or nothing be declared? What exchange rate
11351 should be used when calculating taxes? Would receivers have to pay
11352 income tax if the foundation were to pay Skolelinux contributors in
11353 BitCoin? I have no idea, but it would be interesting to know.
</p
>
11355 <p
>For a currency to be useful and successful, it must be trusted and
11356 accepted by a lot of users. It must be possible to get easy access to
11357 the currency (as a wage or using currency exchanges), and it must be
11358 easy to spend it. At the moment BitCoin seem fairly easy to get
11359 access to, but there are very few places to spend it. I am not really
11360 a regular user of any of the vendor types currently accepting BitCoin,
11361 so I wonder when my kind of shop would start accepting BitCoins. I
11362 would like to buy electronics, travels and subway tickets, not herbs
11363 and books. :) The currency is young, and this will improve over time
11364 if it become popular, but I suspect regular banks will start to lobby
11365 to get BitCoin declared illegal if it become popular. I
'm sure they
11366 will claim it is helping fund terrorism and money laundering (which
11367 probably would be true, as is any currency in existence), but I
11368 believe the problems should be solved elsewhere and not by blaming
11369 currencies.
</p
>
11371 <p
>The process of creating new BitCoins is called mining, and it is
11372 CPU intensive process that depend on a bit of luck as well (as one is
11373 competing against all the other miners currently spending CPU cycles
11374 to see which one get the next lump of cash). The
"winner
" get
50
11375 BitCoin when this happen. Yesterday I came across the obvious way to
11376 join forces to increase ones changes of getting at least some coins,
11377 by coordinating the work on mining BitCoins across several machines
11378 and people, and sharing the result if one is lucky and get the
50
11379 BitCoins. Check out
11380 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
11381 if this sounds interesting. I have not had time to try to set up a
11382 machine to participate there yet, but have seen that running on ones
11383 own for a few days have not yield any BitCoins througth mining
11386 <p
>Update
2010-
12-
15: Found an
<a
11387 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
11388 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
11389 it was interesting to read. The arguments presented seem to be
11390 equally valid for gold, which was used as a currency for many years.
</p
>
11395 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
11396 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
11397 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
11398 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
11399 <description><p
>With this weeks lawless
11400 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
11401 attacks
</a
> on Wikileak and
11402 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
11403 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
11404 not be trusted to handle money transactions.
11406 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
11407 Phipps on bitcoin
</a
> reminded me about a project that a friend of
11408 mine mentioned earlier. I decided to follow Simon
's example, and get
11409 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
11410 some help from my friend to get it all running, and he even handed me
11411 some bitcoins to get started. I even donated a few bitcoins to Simon
11412 for helping me remember BitCoin.
</p
>
11414 <p
>So, what is bitcoins, you probably wonder? It is a digital
11415 crypto-currency, decentralised and handled using peer-to-peer
11416 networks. It allows anonymous transactions and prohibits central
11417 control over the transactions, making it impossible for governments
11418 and companies alike to block donations and other transactions. The
11419 source is free software, and while the key dependency wxWidgets
2.9
11420 for the graphical user interface is missing in Debian, the command
11421 line client builds just fine. Hopefully Jonas
11422 <a href=
"http://bugs.debian.org/
578157">will get the package into
11423 Debian
</a
> soon.
</p
>
11425 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
11426 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
11427 bitcoins
</a
> when selling services and goods, and there are even
11428 currency
"stock
" markets where the exchange rate is decided. There
11429 are not many users so far, but the concept seems promising. If you
11430 want to get started and lack a friend with any bitcoins to spare,
11432 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
11433 bitcoin at the time of writing). Use
11434 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
11435 on the current exchange rates.
</p
>
11437 <p
>As an experiment, I have decided to set up bitcoind on one of my
11438 machines. If you want to support my activity, please send Bitcoin
11439 donations to the address
11440 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
11445 <title>Why isn
't Debian Edu using VLC?
</title>
11446 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
11447 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
11448 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
11449 <description><p
>In the latest issue of Linux Journal, the readers choices were
11450 presented, and the winner among the multimedia player were VLC.
11451 Personally, I like VLC, and it is my player of choice when I first try
11452 to play a video file or stream. Only if VLC fail will I drag out
11453 gmplayer to see if it can do better. The reason is mostly the failure
11454 model and trust. When VLC fail, it normally pop up a error message
11455 reporting the problem. When mplayer fail, it normally segfault or
11456 just hangs. The latter failure mode drain my trust in the program.
<p
>
11458 <p
>But even if VLC is my player of choice, we have choosen to use
11459 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
11460 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
11461 plugin to play web videos seamlessly, and the VLC browser plugin is
11462 not very good. For example, it lack in-line control buttons, so there
11463 is no way for the user to pause the video. Also, when I
11464 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
11465 tested the browser plugins
</a
> available in Debian, the VLC plugin
11466 failed on several video pages where mplayer based plugins worked. If
11467 the browser plugin for VLC was as good as the gecko-mediaplayer
11468 package (which uses mplayer), we would switch.
</P
>
11470 <p
>While VLC is a good player, its user interface is slightly
11471 annoying. The most annoying feature is its inconsistent use of
11472 keyboard shortcuts. When the player is in full screen mode, its
11473 shortcuts are different from when it is playing the video in a window.
11474 For example, space only work as pause when in full screen mode. I
11475 wish it had consisten shortcuts and that space also would work when in
11476 window mode. Another nice shortcut in gmplayer is [enter] to restart
11477 the current video. It is very nice when playing short videos from the
11478 web and want to restart it when new people arrive to have a look at
11479 what is going on.
</p
>
11484 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
11485 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
11486 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</guid>
11487 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
11488 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
11489 upgrade testing of the
11490 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
11491 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
11492 This seem like a very good idea, so I adjusted by test scripts and
11493 can now present the updated result from today:
</p
>
11495 <p
>This is for Gnome:
</p
>
11497 <p
>Installed using apt-get, missing with aptitude
</p
>
11499 <blockquote
><p
>
11504 browser-plugin-gnash
11511 freedesktop-sound-theme
11513 gconf-defaults-service
11526 gnome-codec-install
11528 gnome-desktop-environment
11532 gnome-session-canberra
11534 gnome-themes-extras
11537 gstreamer0.10-fluendo-mp3
11538 gstreamer0.10-tools
11540 gtk2-engines-pixbuf
11541 gtk2-engines-smooth
11543 libapache2-mod-dnssd
11546 libaprutil1-dbd-sqlite3
11549 libboost-date-time1.42
.0
11550 libboost-python1.42
.0
11551 libboost-thread1.42
.0
11553 libchamplain-gtk-
0.4-
0
11555 libclutter-gtk-
0.10-
0
11562 libfreerdp-plugins-standard
11575 libgnome-vfs2.0-cil
11577 libgnomepanel2.24-cil
11582 libgtksourceview2.0-common
11583 libmono-addins-gui0.2-cil
11584 libmono-addins0.2-cil
11585 libmono-cairo2.0-cil
11586 libmono-corlib2.0-cil
11587 libmono-i18n-west2.0-cil
11588 libmono-posix2.0-cil
11589 libmono-security2.0-cil
11590 libmono-sharpzip2.84-cil
11591 libmono-system2.0-cil
11594 libndesk-dbus-glib1.0-cil
11595 libndesk-dbus1.0-cil
11605 libtelepathy-farsight0
11614 nautilus-sendto-empathy
11618 python-aptdaemon-gtk
11620 python-beautifulsoup
11635 python-gtksourceview2
11646 python-pkg-resources
11653 python-twisted-conch
11654 python-twisted-core
11659 python-zope.interface
11661 remmina-plugin-data
11664 rhythmbox-plugin-cdrecorder
11671 system-config-printer-udev
11673 telepathy-mission-control-
5
11680 transmission-common
11684 </p
></blockquote
>
11686 <p
>Installed using apt-get, removed with aptitude
</p
>
11688 <blockquote
><p
>
11692 epiphany-extensions
11694 fast-user-switch-applet
11713 libgtksourceview2.0-
0
11715 libsdl1.2debian-alsa
11721 system-config-printer
11726 </p
></blockquote
>
11728 <p
>Installed using aptitude, missing with apt-get
</p
>
11730 <blockquote
><p
>
11731 gstreamer0.10-gnomevfs
11732 </p
></blockquote
>
11734 <p
>Installed using aptitude, removed with apt-get
</p
>
11736 <blockquote
><p
>
11738 </p
></blockquote
>
11740 <p
>This is for KDE:
</p
>
11742 <p
>Installed using apt-get, missing with aptitude
</p
>
11744 <blockquote
><p
>
11746 </p
></blockquote
>
11748 <p
>Installed using apt-get, removed with aptitude
</p
>
11750 <blockquote
><p
>
11752 network-manager-kde
11753 </p
></blockquote
>
11755 <p
>Installed using aptitude, missing with apt-get
</p
>
11757 <blockquote
><p
>
11771 kdeartwork-emoticons
11773 kdeartwork-theme-icon
11777 kdebase-workspace-bin
11778 kdebase-workspace-data
11790 konqueror-nsplugins
11792 kscreensaver-xsavers
11807 plasma-dataengines-workspace
11809 plasma-desktopthemes-artwork
11810 plasma-runners-addons
11811 plasma-scriptengine-googlegadgets
11812 plasma-scriptengine-python
11813 plasma-scriptengine-qedje
11814 plasma-scriptengine-ruby
11815 plasma-scriptengine-webkit
11816 plasma-scriptengines
11817 plasma-wallpapers-addons
11818 plasma-widget-folderview
11819 plasma-widget-networkmanagement
11822 update-notifier-kde
11823 xscreensaver-data-extra
11825 xscreensaver-gl-extra
11826 xscreensaver-screensaver-bsod
11827 </p
></blockquote
>
11829 <p
>Installed using aptitude, removed with apt-get
</p
>
11831 <blockquote
><p
>
11833 google-gadgets-common
11851 libggadget-qt-
1.0-
0b
11856 libkonqsidebarplugin4a
11860 libkunitconversion4
11865 libplasma-geolocation-interface4
11867 libplasmagenericshell4
11881 libsmokeknewstuff2-
3
11882 libsmokeknewstuff3-
3
11884 libsmokektexteditor3
11892 libsmokeqtnetwork4-
3
11893 libsmokeqtopengl4-
3
11894 libsmokeqtscript4-
3
11898 libsmokeqtuitools4-
3
11899 libsmokeqtwebkit4-
3
11910 plasma-dataengines-addons
11911 plasma-scriptengine-superkaramba
11912 plasma-widget-lancelot
11913 plasma-widgets-addons
11914 plasma-widgets-workspace
11918 update-notifier-common
11919 </p
></blockquote
>
11921 <p
>Running apt-get autoremove made the results using apt-get and
11922 aptitude a bit more similar, but there are still quite a lott of
11923 differences. I have no idea what packages should be installed after
11924 the upgrade, but hope those that do can have a look.
</p
>
11929 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
11930 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
11931 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
11932 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
11933 <description><p
>Most of the computers in use by the
11934 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
11935 are virtual machines. And they have been Xen machines running on a
11936 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
11937 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
11938 bit harder that it could have been, because we set up the Xen virtual
11939 machines to get the virtual partitions from LVM, which as far as I
11940 know is not supported by KVM. So to migrate, we had to convert
11941 several LVM logical volumes to partitions on a virtual disk file.
</p
>
11944 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
11945 nice recipe
</a
> to do this, and wrote the following script to do the
11946 migration. It uses qemu-img from the qemu package to make the disk
11947 image, parted to partition it, losetup and kpartx to present the disk
11948 image partions as devices, and dd to copy the data. I NFS mounted the
11949 new servers storage area on the old server to do the migration.
</p
>
11955 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
11960 if [ -z
"$
1" ] ; then
11961 echo
"Usage: $
0 &lt;hostname
&gt;
"
11964 host=
"$
1"
11967 if [ ! -e /dev/vg_data/$host-disk ] ; then
11968 echo
"error: unable to find LVM volume for $host
"
11972 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
11973 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11974 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11975 totalsize=$(( ( $disksize + $swapsize ) ))
11978 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
11979 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
11981 parted $img mklabel msdos
11982 parted $img mkpart primary linux-swap
0 $disksize
11983 parted $img mkpart primary ext2 $disksize $totalsize
11984 parted $img set
1 boot on
11987 losetup /dev/loop0 $img
11988 kpartx -a /dev/loop0
11990 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
11991 fsck.ext3 -f /dev/mapper/loop0p1 || true
11992 mkswap /dev/mapper/loop0p2
11994 kpartx -d /dev/loop0
11995 losetup -d /dev/loop0
11998 <p
>The script is perhaps so simple that it is not copyrightable, but
11999 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
12001 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
12002 the new disk image attached, installed grub-pc and linux-image-
686 and
12003 set up grub to boot from the disk image. After this, the KVM machines
12004 seem to work just fine.
</p
>
12009 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
12010 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
12011 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
12012 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
12013 <description><p
>I
'm still running upgrade testing of the
12014 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
12015 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
12016 status. Here is a short update based on a test I ran
20101118.
</p
>
12018 <p
>I still do not know what a correct migration should look like, so I
12019 report any differences between apt and aptitude and hope someone else
12020 can see if anything should be changed.
</p
>
12022 <p
>This is for Gnome:
</p
>
12024 <p
>Installed using apt-get, missing with aptitude
</p
>
12026 <blockquote
><p
>
12027 apache2.2-bin aptdaemon at-spi baobab binfmt-support
12028 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
12029 dmz-cursor-theme empathy empathy-common finger
12030 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
12031 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
12032 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
12033 gnome-cards-data gnome-codec-install gnome-core
12034 gnome-desktop-environment gnome-disk-utility gnome-screenshot
12035 gnome-search-tool gnome-session-canberra gnome-spell
12036 gnome-system-log gnome-themes-extras gnome-themes-more
12037 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
12038 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
12039 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
12040 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
12041 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
12042 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
12043 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
12044 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
12045 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
12046 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
12047 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
12048 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
12049 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
12050 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
12051 libgtk2.0-cil libgtkglext1 libgtksourceview-common
12052 libgtksourceview2.0-common libmono-addins-gui0.2-cil
12053 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
12054 libmono-i18n-west2.0-cil libmono-posix2.0-cil
12055 libmono-security2.0-cil libmono-sharpzip2.84-cil
12056 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
12057 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
12058 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
12059 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
12060 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
12061 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
12062 libxalan2-java libxerces2-java media-player-info mesa-utils
12063 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
12064 nautilus-sendto-empathy openoffice.org-writer2latex
12065 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
12066 python-aptdaemon python-aptdaemon-gtk python-axiom
12067 python-beautifulsoup python-bugbuddy python-clientform
12068 python-coherence python-configobj python-crypto python-cupshelpers
12069 python-cupsutils python-eggtrayicon python-elementtree
12070 python-epsilon python-evolution python-feedparser python-gdata
12071 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
12072 python-gtksourceview2 python-httplib2 python-louie python-mako
12073 python-markupsafe python-mechanize python-nevow python-notify
12074 python-opengl python-openssl python-pam python-pkg-resources
12075 python-pyasn1 python-pysqlite2 python-rdflib python-serial
12076 python-tagpy python-twisted-bin python-twisted-conch
12077 python-twisted-core python-twisted-web python-utidylib python-webkit
12078 python-xdg python-zope.interface remmina remmina-plugin-data
12079 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
12080 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
12081 software-center svgalibg1 system-config-printer-udev
12082 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
12083 totem totem-coherence totem-mozilla totem-plugins
12084 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
12086 </p
></blockquote
>
12088 Installed using apt-get, removed with aptitude
12090 <blockquote
><p
>
12091 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
12092 epiphany-extensions epiphany-gecko evolution-exchange
12093 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
12094 gedit-common gnome-app-install gnome-games gnome-games-data
12095 gnome-nettool gnome-system-tools gnome-themes gnome-utils
12096 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
12097 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
12098 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
12099 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
12100 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
12101 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
12102 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
12103 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
12104 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
12105 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
12106 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
12107 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
12108 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
12109 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
12110 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
12111 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
12112 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
12113 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
12114 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
12115 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
12116 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
12117 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
12118 sound-juicer swfdec-gnome system-config-printer totem-common
12119 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
12120 </p
></blockquote
>
12122 <p
>Installed using aptitude, missing with apt-get
</p
>
12124 <blockquote
><p
>
12125 gstreamer0.10-gnomevfs
12126 </p
></blockquote
>
12128 <p
>Installed using aptitude, removed with apt-get
</p
>
12130 <blockquote
><p
>
12132 </p
></blockquote
>
12134 <p
>This is for KDE:
</p
>
12136 <p
>Installed using apt-get, missing with aptitude
</p
>
12138 <blockquote
><p
>
12139 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
12140 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
12141 ghostscript-x git gnome-audio gnugo granatier gs-common
12142 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
12143 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
12144 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
12145 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12146 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
12147 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
12148 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12149 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
12150 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
12151 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
12152 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
12153 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
12154 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
12155 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
12156 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
12157 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
12158 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
12159 libkrossui4 libmailtools-perl libmime-tools-perl
12160 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
12161 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
12162 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
12163 lirc luatex marble networkstatus noatun-plugins
12164 openoffice.org-writer2latex palapeli palapeli-data parley
12165 parley-data poster psutils pulseaudio pulseaudio-esound-compat
12166 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
12167 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
12168 ttf-sazanami-gothic
12169 </p
></blockquote
>
12171 <p
>Installed using apt-get, removed with aptitude
</p
>
12173 <blockquote
><p
>
12174 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
12175 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
12176 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
12177 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
12178 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
12179 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
12180 kitchensync kiten kjumpingcube klatin klettres klickety klines
12181 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
12182 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
12183 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
12184 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
12185 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
12186 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
12187 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
12188 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
12189 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12190 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
12191 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
12192 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12193 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
12194 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
12195 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
12196 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
12197 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12198 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
12199 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
12200 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
12201 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
12202 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
12203 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
12204 mpeglib network-manager-kde noatun pmount tex-common texlive-base
12205 texlive-common texlive-doc-base texlive-fonts-recommended tidy
12206 ttf-dustin ttf-kochi-gothic ttf-sjfonts
12207 </p
></blockquote
>
12209 <p
>Installed using aptitude, missing with apt-get
</p
>
12211 <blockquote
><p
>
12212 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
12213 kdeartwork kdebase kdebase-apps kdebase-workspace
12214 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
12215 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
12216 netpbm plasma-widget-folderview plasma-widget-networkmanagement
12217 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
12218 xscreensaver-screensaver-bsod
12219 </p
></blockquote
>
12221 <p
>Installed using aptitude, removed with apt-get
</p
>
12223 <blockquote
><p
>
12224 kdebase-bin konq-plugins konqueror
12225 </p
></blockquote
>
12230 <title>Gnash buildbot slave and Debian kfreebsd
</title>
12231 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
12232 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
12233 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
12234 <description><p
>Answering
12235 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
12236 call from the Gnash project
</a
> for
12237 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
12238 current source, I have set up a virtual KVM machine on the Debian
12239 Edu/Skolelinux virtualization host to test the git source on
12240 Debian/Squeeze. I hope this can help the developers in getting new
12241 releases out more often.
</p
>
12243 <p
>As the developers want less main-stream build platforms tested to,
12244 I have considered setting up a
<a
12245 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
12246 machine as well. I have also considered using the kfreebsd
12247 architecture in Debian as a file server in NUUG to get access to the
5
12248 TB zfs volume we currently use to store DV video. Because of this, I
12249 finally got around to do a test installation of Debian/Squeeze with
12250 kfreebsd. Installation went fairly smooth, thought I noticed some
12251 visual glitches in the cdebconf dialogs (black cursor left on the
12252 screen at random locations). Have not gotten very far with the
12253 testing. Noticed cfdisk did not work, but fdisk did so it was not a
12254 fatal problem. Have to spend some more time on it to see if it is
12255 useful as a file server for NUUG. Will try to find time to set up a
12256 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
12261 <title>Debian in
3D
</title>
12262 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
12263 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
12264 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
12265 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
12267 <p
>3D printing is just great. I just came across this Debian logo in
12269 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
12270 thingiverse blog
</a
>.
</p
>
12275 <title>Software updates
2010-
10-
24</title>
12276 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
12277 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
12278 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
12279 <description><p
>Some updates.
</p
>
12281 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
12282 raise money for the project is going well. The lower limit of
10
12283 signers was reached in
24 hours, and so far
13 people have signed it.
12284 More signers and more funding is most welcome, and I am really curious
12285 how far we can get before the time limit of December
24 is reached.
12288 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
12289 about what appear to be a great code coverage tool capable of
12290 generating code coverage stats without any changes to the source code.
12292 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
12293 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
12294 It is missing in Debian, but the git source built just fine in Squeeze
12295 after I installed libelf-dev, libdwarf-dev, pkg-config and
12296 libglib2.0-dev. Failed to build in Lenny, but suspect that is
12297 solvable. I hope kcov make it into Debian soon.
</p
>
12299 <p
>Finally found time to wrap up the release notes for
<a
12300 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
12301 new alpha release of Debian Edu
</a
>, and just published the second
12302 alpha test release of the Squeeze based Debian Edu /
12303 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
12304 release. Give it a try if you need a complete linux solution for your
12305 school, including central infrastructure server, workstations, thin
12306 client servers and diskless workstations. A nice touch added
12307 yesterday is RDP support on the thin client servers, for windows
12308 clients to get a Linux desktop on request.
</p
>
12313 <title>Some notes on Flash in Debian and Debian Edu
</title>
12314 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
12315 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
12316 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
12317 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
12318 popularity-contest numbers
</a
>, the adobe-flashplugin package the
12319 second most popular used package that is missing in Debian. The sixth
12320 most popular is flashplayer-mozilla. This is a clear indication that
12321 working flash is important for Debian users. Around
10 percent of the
12322 users submitting data to popcon.debian.org have this package
12323 installed.
</p
>
12325 <p
>In the report written by Lars Risan in August
2008
12326 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
12327 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
12328 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
12329 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
12330 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
12331 web sites require Flash to work, and lacking working Flash support in
12332 the web browser and the problems with installing it was perceived as a
12333 good reason to stay with Windows.
</p
>
12335 <p
>I once saw a funny and sad comment in a web forum, where Linux was
12336 said to be the retarded cousin that did not really understand
12337 everything you told him but could work fairly well. This was a
12338 comment regarding the problems Linux have with proprietary formats and
12339 non-standard web pages, and is sad because it exposes a fairly common
12340 understanding of whose fault it is if web pages that only work in for
12341 example Internet Explorer
6 fail to work on Firefox, and funny because
12342 it explain very well how annoying it is for users when Linux
12343 distributions do not work with the documents they receive or the web
12344 pages they want to visit.
</p
>
12346 <p
>This is part of the reason why I believe it is important for Debian
12347 and Debian Edu to have a well working Flash implementation in the
12348 distribution, to get at least popular sites as Youtube and Google
12349 Video to working out of the box. For Squeeze, Debian have the chance
12350 to include the latest version of Gnash that will make this happen, as
12351 the new release
0.8.8 was published a few weeks ago and is resting in
12352 unstable. The new version work with more sites that version
0.8.7.
12353 The Gnash maintainers have asked for a freeze exception, but the
12354 release team have not had time to reply to it yet. I hope they agree
12355 with me that Flash is important for the Debian desktop users, and thus
12356 accept the new package into Squeeze.
</p
>
12361 <title>Circular package dependencies harms apt recovery
</title>
12362 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
12363 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
12364 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
12365 <description><p
>I discovered this while doing
12366 <a href=
"https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
12367 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
12368 in Debian still got circular dependencies, and it is often claimed
12369 that apt and aptitude should be able to handle this just fine, but
12370 some times these dependency loops causes apt to fail.
</p
>
12372 <p
>An example is from todays
12373 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
12374 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
12375 causes perl-modules to fail to upgrade. The cause is simple. If a
12376 package fail to unpack, then only part of packages with the circular
12377 dependency might end up being unpacked when unpacking aborts, and the
12378 ones already unpacked will fail to configure in the recovery phase
12379 because its dependencies are unavailable.
</p
>
12381 <p
>In this log, the problem manifest itself with this error:
</p
>
12383 <blockquote
><pre
>
12384 dpkg: dependency problems prevent configuration of perl-modules:
12385 perl-modules depends on perl (
>=
5.10.1-
1); however:
12386 Version of perl on system is
5.10.0-
19lenny
2.
12387 dpkg: error processing perl-modules (--configure):
12388 dependency problems - leaving unconfigured
12389 </pre
></blockquote
>
12391 <p
>The perl/perl-modules circular dependency is already
12392 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
12393 hopefully be solved as soon as possible, but it is not the only one,
12394 and each one of these loops in the dependency tree can cause similar
12395 failures. Of course, they only occur when there are bugs in other
12396 packages causing the unpacking to fail, but it is rather nasty when
12397 the failure of one package causes the problem to become worse because
12398 of dependency loops.
</p
>
12401 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
12402 tireless effort by Bill Allombert
</a
>, the number of circular
12404 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
12405 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
12407 <p
>Todays testing also exposed a bug in
12408 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
12409 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
12410 apt-get and aptitude, the latter possibly caused by some circular
12411 dependency. Reported both to BTS to try to get someone to look at
12417 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
12418 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
12419 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
12420 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
12421 <description><p
>This is a
12422 <a href=
"https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
12424 <a href=
"https://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
12426 <a href=
"https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
12427 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
12429 <p
>As a step to try to see if it possible to merge the DNS and DHCP
12430 LDAP objects, I have had a look at how the packages pdns-backend-ldap
12431 and dhcp3-server-ldap in Debian use the LDAP server. The two
12432 implementations are quite different in how they use LDAP.
</p
>
12434 To get this information, I started slapd with debugging enabled and
12435 dumped the debug output to a file to get the LDAP searches performed
12436 on a Debian Edu main-server. Here is a summary.
12438 <p
><strong
>powerdns
</strong
></p
>
12440 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
12441 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
12444 <p
>PowerDNS have two modes of operation using LDAP as its backend.
12445 One
"strict
" mode where the forward and reverse DNS lookups are done
12446 using the same LDAP objects, and a
"tree
" mode where the forward and
12447 reverse entries are in two different subtrees in LDAP with a structure
12448 based on the DNS names, as in tjener.intern and
12449 2.2.0.10.in-addr.arpa.
</p
>
12451 <p
>In tree mode, the server is set up to use a LDAP subtree as its
12452 base, and uses a
"base
" scoped search for the DNS name by adding
12453 "dc=tjener,dc=intern,
" to the base with a filter for
12454 "(associateddomain=tjener.intern)
" for the forward entry and
12455 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
12456 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
12457 forward entries, it is looking for attributes named dnsttl, arecord,
12458 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
12459 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
12460 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
12461 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
12462 spfrecord and modifytimestamp. For reverse entries it is looking for
12463 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
12464 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
12465 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
12466 ldapsearch commands could look like this:
</p
>
12468 <blockquote
><pre
>
12469 ldapsearch -h ldap \
12470 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
12471 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
12472 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
12473 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
12474 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
12475 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
12477 ldapsearch -h ldap \
12478 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
12479 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
12480 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
12481 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
12482 srvrecord naptrrecord modifytimestamp
12483 </pre
></blockquote
>
12485 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
12486 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
12487 example LDAP objects used there. In addition to these objects, the
12488 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
12489 also exist.
</p
>
12491 <blockquote
><pre
>
12492 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
12494 objectclass: dnsdomain
12495 objectclass: domainrelatedobject
12498 associateddomain: tjener.intern
12500 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
12502 objectclass: dnsdomain2
12503 objectclass: domainrelatedobject
12505 ptrrecord: tjener.intern
12506 associateddomain:
2.2.0.10.in-addr.arpa
12507 </pre
></blockquote
>
12509 <p
>In strict mode, the server behaves differently. When looking for
12510 forward DNS entries, it is doing a
"subtree
" scoped search with the
12511 same base as in the tree mode for a object with filter
12512 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
12513 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
12514 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
12515 naptrrecord and modifytimestamp. For reverse entires it also do a
12516 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
12517 and the requested attributes are associateddomain, dnsttl and
12518 modifytimestamp. In short, in strict mode the objects with ptrrecord
12519 go away, and the arecord attribute in the forward object is used
12522 <p
>The forward and reverse searches can be simulated using ldapsearch
12523 like this:
</p
>
12525 <blockquote
><pre
>
12526 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
12527 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
12528 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
12529 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
12530 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
12531 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
12533 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
12534 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
12535 </pre
></blockquote
>
12537 <p
>In addition to the forward and reverse searches , there is also a
12538 search for SOA records, which behave similar to the forward and
12539 reverse lookups.
</p
>
12541 <p
>A thing to note with the PowerDNS behaviour is that it do not
12542 specify any objectclass names, and instead look for the attributes it
12543 need to generate a DNS reply. This make it able to work with any
12544 objectclass that provide the needed attributes.
</p
>
12546 <p
>The attributes are normally provided in the cosine (RFC
1274) and
12547 dnsdomain2 schemas. The latter is used for reverse entries like
12548 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
12550 <p
>In Debian Edu, we have created DNS objects using the object classes
12551 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
12552 attributes) and domainrelatedobject (for associatedDomain). The use
12553 of structural object classes make it impossible to combine these
12554 classes with the object classes used by DHCP.
</p
>
12556 <p
>There are other schemas that could be used too, for example the
12557 dnszone structural object class used by Gosa and bind-sdb for the DNS
12558 attributes combined with the domainrelatedobject object class, but in
12559 this case some unused attributes would have to be included as well
12560 (zonename and relativedomainname).
</p
>
12562 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
12563 mode and not use any of the existing objectclasses (dnsdomain,
12564 dnsdomain2 and dnszone) when one want to combine the DNS information
12565 with DHCP information, and instead create a auxiliary object class
12566 defined something like this (using the attributes defined for
12567 dnsdomain and dnsdomain2 or dnszone):
</p
>
12569 <blockquote
><pre
>
12570 objectclass ( some-oid NAME
'dnsDomainAux
'
12573 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
12574 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
12575 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
12576 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
12577 A6Record $ DNAMERecord
12579 </pre
></blockquote
>
12581 <p
>This will allow any object to become a DNS entry when combined with
12582 the domainrelatedobject object class, and allow any entity to include
12583 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
12584 developers asking for their view on this schema and if they are
12585 interested in providing such schema with PowerDNS, and I hope my
12586 message will be accepted into their mailing list soon.
</p
>
12588 <p
><strong
>ISC dhcp
</strong
></p
>
12590 <p
>The DHCP server searches for specific objectclass and requests all
12591 the object attributes, and then uses the attributes it want. This
12592 make it harder to figure out exactly what attributes are used, but
12593 thanks to the working example in Debian Edu I can at least get an idea
12594 what is needed without having to read the source code.
</p
>
12596 <p
>In the DHCP server configuration, the LDAP base to use and the
12597 search filter to use to locate the correct dhcpServer entity is
12598 stored. These are the relevant entries from
12599 /etc/dhcp3/dhcpd.conf:
</p
>
12601 <blockquote
><pre
>
12602 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
12603 ldap-dhcp-server-cn
"dhcp
";
12604 </pre
></blockquote
>
12606 <p
>The DHCP server uses this information to nest all the DHCP
12607 configuration it need. The cn
"dhcp
" is located using the given LDAP
12608 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
12609 search result is this entry:
</p
>
12611 <blockquote
><pre
>
12612 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
12615 objectClass: dhcpServer
12616 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12617 </pre
></blockquote
>
12619 <p
>The content of the dhcpServiceDN attribute is next used to locate the
12620 subtree with DHCP configuration. The DHCP configuration subtree base
12621 is located using a base scope search with base
"cn=DHCP
12622 Config,dc=skole,dc=skolelinux,dc=no
" and filter
12623 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
12624 The search result is this entry:
</p
>
12626 <blockquote
><pre
>
12627 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12630 objectClass: dhcpService
12631 objectClass: dhcpOptions
12632 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
12633 dhcpStatements: ddns-update-style none
12634 dhcpStatements: authoritative
12635 dhcpOption: smtp-server code
69 = array of ip-address
12636 dhcpOption: www-server code
72 = array of ip-address
12637 dhcpOption: wpad-url code
252 = text
12638 </pre
></blockquote
>
12640 <p
>Next, the entire subtree is processed, one level at the time. When
12641 all the DHCP configuration is loaded, it is ready to receive requests.
12642 The subtree in Debian Edu contain objects with object classes
12643 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
12644 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
12645 and information about netmasks, dynamic range etc. Leaving out the
12646 details here because it is not relevant for the focus of my
12647 investigation, which is to see if it is possible to merge dns and dhcp
12648 related computer objects.
</p
>
12650 <p
>When a DHCP request come in, LDAP is searched for the MAC address
12651 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
12652 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
12653 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
12654 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
12657 <blockquote
><pre
>
12658 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12661 objectClass: dhcpHost
12662 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
12663 dhcpStatements: fixed-address hostname
12664 </pre
></blockquote
>
12666 <p
>There is less flexiblity in the way LDAP searches are done here.
12667 The object classes need to have fixed names, and the configuration
12668 need to be stored in a fairly specific LDAP structure. On the
12669 positive side, the invidiual dhcpHost entires can be anywhere without
12670 the DN pointed to by the dhcpServer entries. The latter should make
12671 it possible to group all host entries in a subtree next to the
12672 configuration entries, and this subtree can also be shared with the
12673 DNS server if the schema proposed above is combined with the dhcpHost
12674 structural object class.
12676 <p
><strong
>Conclusion
</strong
></p
>
12678 <p
>The PowerDNS implementation seem to be very flexible when it come
12679 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
12680 come to the the LDAP structure, the
"strict
" mode is very flexible,
12681 allowing DNS objects to be stored anywhere under the base cn specified
12682 in the configuration.
</p
>
12684 <p
>The DHCP implementation on the other hand is very inflexible, both
12685 regarding which LDAP schemas to use and which LDAP structure to use.
12686 I guess one could implement ones own schema, as long as the
12687 objectclasses and attributes have the names used, but this do not
12688 really help when the DHCP subtree need to have a fairly fixed
12689 structure.
</p
>
12691 <p
>Based on the observed behaviour, I suspect a LDAP structure like
12692 this might work for Debian Edu:
</p
>
12694 <blockquote
><pre
>
12696 cn=machine-info (dhcpService) - dhcpServiceDN points here
12697 cn=dhcp (dhcpServer)
12698 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
12699 cn=
10.0.2.0 (dhcpSubnet)
12700 cn=group1 (dhcpGroup/dhcpOptions)
12701 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
12702 cn=
192.168.0.0 (dhcpSubnet)
12703 cn=group1 (dhcpGroup/dhcpOptions)
12704 ou=machines - PowerDNS base points here
12705 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
12706 </pre
></blockquote
>
12708 <P
>This is not tested yet. If the DHCP server require the dhcpHost
12709 entries to be in the dhcpGroup subtrees, the entries can be stored
12710 there instead of a common machines subtree, and the PowerDNS base
12711 would have to be moved one level up to the machine-info subtree.
</p
>
12713 <p
>The combined object under the machines subtree would look something
12714 like this:
</p
>
12716 <blockquote
><pre
>
12717 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
12720 objectClass: dhcpHost
12721 objectclass: domainrelatedobject
12722 objectclass: dnsDomainAux
12723 associateddomain: hostname.intern
12724 arecord:
10.11.12.13
12725 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
12726 dhcpStatements: fixed-address hostname.intern
12727 </pre
></blockquote
>
12729 </p
>One could even add the LTSP configuration associated with a given
12730 machine, as long as the required attributes are available in a
12731 auxiliary object class.
</p
>
12736 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
12737 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
12738 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
12739 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
12740 <description><p
>For a while now, I have wanted to find a way to change the DNS and
12741 DHCP services in Debian Edu to use the same LDAP objects for a given
12742 computer, to avoid the possibility of having a inconsistent state for
12743 a computer in LDAP (as in DHCP but no DNS entry or the other way
12744 around) and make it easier to add computers to LDAP.
</p
>
12746 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
12747 information finally found a solution that seem to work.
</p
>
12749 <p
>The old setup required three LDAP objects for a given computer.
12750 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
12751 we switch powerdns to use its strict LDAP method (ldap-method=strict
12752 in pdns-debian-edu.conf), the forward and reverse DNS entries are
12753 merged into one while making it impossible to transfer the reverse map
12754 to a slave DNS server.
</p
>
12756 <p
>If we also replace the object class used to get the DNS related
12757 attributes to one allowing these attributes to be combined with the
12758 dhcphost object class, we can merge the DNS and DHCP entries into one.
12759 I
've written such object class in the dnsdomainaux.schema file (need
12760 proper OIDs, but that is a minor issue), and tested the setup. It
12761 seem to work.
</p
>
12763 <p
>With this test setup in place, we can get away with one LDAP object
12764 for both DNS and DHCP, and even the LTSP configuration I suggested in
12765 an earlier email. The combined LDAP object will look something like
12768 <blockquote
><pre
>
12769 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12771 objectClass: dhcphost
12772 objectclass: domainrelatedobject
12773 objectclass: dnsdomainaux
12774 associateddomain: hostname.intern
12775 arecord:
10.11.12.13
12776 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
12777 dhcpstatements: fixed-address hostname
12779 </pre
></blockquote
>
12781 <p
>The DNS server uses the associateddomain and arecord entries, while
12782 the DHCP server uses the dhcphwaddress and dhcpstatements entries
12783 before asking DNS to resolve the fixed-adddress. LTSP will use
12784 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
12786 <p
>I am not yet sure if I can get the DHCP server to look for its
12787 dhcphost in a different location, to allow us to put the objects
12788 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
12789 that. If I can
't figure out a way to do that, we can still get rid of
12790 the hosts subtree and move all its content into the DHCP Config tree
12791 (which probably should be renamed to be more related to the new
12792 content. I suspect cn=dnsdhcp,ou=services or something like that
12793 might be a good place to put it.
</p
>
12795 <p
>If you want to help out with implementing this for Debian Edu,
12796 please contact us on debian-edu@lists.debian.org.
</p
>
12801 <title>Idea for storing LTSP configuration in LDAP
</title>
12802 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
12803 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
12804 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
12805 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
12806 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
12807 clients, and that this can be used to fetch configuration from LDAP if
12808 Debian Edu choose to store configuration there.
</p
>
12810 <p
>Armed with this information, I got inspired and wrote a test module
12811 to get configuration from LDAP. The idea is to look up the MAC
12812 address of the client in LDAP, and look for attributes on the form
12813 ltspconfigsetting=value, and use this to export SETTING=value to the
12814 LTSP clients.
</p
>
12816 <p
>The goal is to be able to store the LTSP configuration attributes
12817 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
12818 allowing us to store all information about a computer in one place.
</p
>
12820 <p
>This is a untested draft implementation, and I welcome feedback on
12821 this approach. A real LDAP schema for the ltspClientAux objectclass
12822 need to be written. Comments, suggestions, etc?
</p
>
12824 <blockquote
><pre
>
12825 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
12827 # Fetch LTSP client settings from LDAP based on MAC address
12829 # Uses ethernet address as stored in the dhcpHost objectclass using
12830 # the dhcpHWAddress attribute or ethernet address stored in the
12831 # ieee802Device objectclass with the macAddress attribute.
12833 # This module is written to be schema agnostic, and only depend on the
12834 # existence of attribute names.
12836 # The LTSP configuration variables are saved directly using a
12837 # ltspConfig prefix and uppercasing the rest of the attribute name.
12838 # To set the SERVER variable, set the ltspConfigServer attribute.
12840 # Some LDAP schema should be created with all the relevant
12841 # configuration settings. Something like this should work:
12843 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
12846 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
12848 LDAPSERVER=$(debian-edu-ldapserver)
12849 if [
"$LDAPSERVER
" ] ; then
12850 LDAPBASE=$(debian-edu-ldapserver -b)
12851 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
12852 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
12853 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
12854 grep
'^ltspConfig
' | while read attr value ; do
12855 # Remove prefix and convert to upper case
12856 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
12857 # bass value on to clients
12858 eval
"$attr=$value; export $attr
"
12862 </pre
></blockquote
>
12864 <p
>I
'm not sure this shell construction will work, because I suspect
12865 the while block might end up in a subshell causing the variables set
12866 there to not show up in ltsp-config, but if that is the case I am sure
12867 the code can be restructured to make sure the variables are passed on.
12868 I expect that can be solved with some testing. :)
</p
>
12870 <p
>If you want to help out with implementing this for Debian Edu,
12871 please contact us on debian-edu@lists.debian.org.
</p
>
12873 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
12874 configuration in LDAP that was created around year
2000 by
12875 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
12876 Xperience, Inc.,
2000</a
>. I found its
12877 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
12878 personal home page over at redhat.com.
</p
>
12883 <title>jXplorer, a very nice LDAP GUI
</title>
12884 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
12885 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
12886 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
12887 <description><p
>Since
12888 <a href=
"https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
12889 last post
</a
> about available LDAP tools in Debian, I was told about a
12890 LDAP GUI that is even better than luma. The java application
12891 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
12892 moving LDAP objects and subtrees using drag-and-drop, and can
12893 authenticate using Kerberos. I have only tested the Kerberos
12894 authentication, but do not have a LDAP setup allowing me to rewrite
12895 LDAP with my test user yet. It is
12896 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
12897 Debian
</a
> testing and unstable at the moment. The only problem I
12898 have with it is how it handle errors. If something go wrong, its
12899 non-intuitive behaviour require me to go through some query work list
12900 and remove the failing query. Nothing big, but very annoying.
</p
>
12905 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
12906 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
12907 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
12908 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
12909 <description><p
>Here is a short update on my
<a
12910 href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
12911 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
12912 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
12913 not reporting the status for KDE, because the upgrade crashes when
12914 aptitude try because of missing conflicts
12915 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
12916 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
12918 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
12919 complete list of the installed packages. Based on this I see these
12920 differences when I did a test run today. As usual, I do not really
12921 know what the correct set of packages would be, but thought it best to
12922 publish the difference.
</p
>
12924 <p
>Installed using apt-get, missing with aptitude
</p
>
12926 <blockquote
><p
>
12927 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
12928 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
12929 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
12930 libgtksourceview-common libpt-
1.10.10-plugins-alsa
12931 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
12932 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
12933 python-
4suite-xml python-eggtrayicon python-gtkhtml2
12934 python-gtkmozembed svgalibg1 xserver-xephyr zip
12935 </p
></blockquote
>
12937 <p
>Installed using apt-get, removed with aptitude
</p
>
12939 <blockquote
><p
>
12940 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
12941 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
12942 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
12943 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
12944 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
12945 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
12946 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
12947 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
12948 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
12949 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
12950 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
12951 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
12952 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
12953 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
12954 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
12955 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
12956 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
12957 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
12958 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
12959 mysql-common swfdec-gnome totem-gstreamer wodim
12960 </p
></blockquote
>
12962 <p
>Installed using aptitude, missing with apt-get
</p
>
12964 <blockquote
><p
>
12965 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
12966 python-gnomekeyring python-wnck rhythmbox-plugins xorg
12967 xserver-xorg-input-all xserver-xorg-input-evdev
12968 xserver-xorg-input-kbd xserver-xorg-input-mouse
12969 xserver-xorg-input-synaptics xserver-xorg-video-all
12970 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
12971 xserver-xorg-video-chips xserver-xorg-video-cirrus
12972 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12973 xserver-xorg-video-glint xserver-xorg-video-i128
12974 xserver-xorg-video-i740 xserver-xorg-video-mach64
12975 xserver-xorg-video-mga xserver-xorg-video-neomagic
12976 xserver-xorg-video-nouveau xserver-xorg-video-nv
12977 xserver-xorg-video-r128 xserver-xorg-video-radeon
12978 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
12979 xserver-xorg-video-s3 xserver-xorg-video-s3virge
12980 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
12981 xserver-xorg-video-sis xserver-xorg-video-sisusb
12982 xserver-xorg-video-tdfx xserver-xorg-video-tga
12983 xserver-xorg-video-trident xserver-xorg-video-tseng
12984 xserver-xorg-video-vesa xserver-xorg-video-vmware
12985 xserver-xorg-video-voodoo
12986 </p
></blockquote
>
12988 <p
>Installed using aptitude, removed with apt-get
</p
>
12990 <blockquote
><p
>
12991 deskbar-applet xserver-xorg xserver-xorg-core
12992 xserver-xorg-input-wacom xserver-xorg-video-intel
12993 xserver-xorg-video-openchrome
12994 </p
></blockquote
>
12996 <p
>I was told on IRC that the xorg-xserver package was
12997 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
12998 in git
</a
> today to try to get apt-get to not remove xorg completely.
12999 No idea when it hits Squeeze, but when it does I hope it will reduce
13000 the difference somewhat.
13005 <title>LUMA, a very nice LDAP GUI
</title>
13006 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
13007 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
13008 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
13009 <description><p
>The last few days I have been looking into the status of the LDAP
13010 directory in Debian Edu, and in the process I started to miss a GUI
13011 tool to browse the LDAP tree. The only one I was able to find in
13012 Debian/Squeeze and Lenny is
13013 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
13014 be a great tool to get a overview of the current LDAP directory
13015 populated by default in Skolelinux. Thanks to it, I have been able to
13016 find empty and obsolete subtrees, misplaced objects and duplicate
13017 objects. It will be installed by default in Debian/Squeeze. If you
13018 are working with LDAP, give it a go. :)
</p
>
13020 <p
>I did notice one problem with it I have not had time to report to
13021 the BTS yet. There is no .desktop file in the package, so the tool do
13022 not show up in the Gnome and KDE menus, but only deep down in in the
13023 Debian submenu in KDE. I hope that can be fixed before Squeeze is
13024 released.
</p
>
13026 <p
>I have not yet been able to get it to modify the tree yet. I would
13027 like to move objects and remove subtrees directly in the GUI, but have
13028 not found a way to do that with LUMA yet. So in the mean time, I use
13029 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
13031 <p
>If you have tips on other GUI tools for LDAP that might be useful
13032 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
13034 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
13035 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
13036 useful GUI alternative. It seem like a good tool, but is unmaintained
13037 in Debian and got a RC bug keeping it out of Squeeze. Unless that
13038 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
13043 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
13044 <link>https://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>
13045 <guid isPermaLink=
"true">https://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>
13046 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
13047 <description><p
>A while back, I
13048 <a href=
"https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
13049 about the fact
</a
> that it is not possible with the provided schemas
13050 for storing DNS and DHCP information in LDAP to combine the two sets
13051 of information into one LDAP object representing a computer.
</p
>
13053 <p
>In the mean time, I discovered that a simple fix would be to make
13054 the dhcpHost object class auxiliary, to allow it to be combined with
13055 the dNSDomain object class, and thus forming one object for one
13056 computer when storing both DHCP and DNS information in LDAP.
</p
>
13058 <p
>If I understand this correctly, it is not safe to do this change
13059 without also changing the assigned number for the object class, and I
13060 do not know enough about LDAP schema design to do that properly for
13061 Debian Edu.
</p
>
13063 <p
>Anyway, for future reference, this is how I believe we could change
13065 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
13066 schema
</a
> to solve at least part of the problem with the LDAP schemas
13067 available today from IETF.
</p
>
13070 --- dhcp.schema (revision
65192)
13071 +++ dhcp.schema (working copy)
13072 @@ -
376,
7 +
376,
7 @@
13073 objectclass (
2.16.840.1.113719.1.203.6.6
13074 NAME
'dhcpHost
'
13075 DESC
'This represents information about a particular client
'
13077 + SUP top AUXILIARY
13079 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
13080 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
13083 <p
>I very much welcome clues on how to do this properly for Debian
13084 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
13085 package, and should thus be free to rewrite it as we see fit.
</p
>
13087 <p
>If you want to help out with implementing this for Debian Edu,
13088 please contact us on debian-edu@lists.debian.org.
</p
>
13093 <title>Calling tasksel like the installer, while still getting useful output
</title>
13094 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
13095 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
13096 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
13097 <description><p
>A few times I have had the need to simulate the way tasksel
13098 installs packages during the normal debian-installer run. Until now,
13099 I have ended up letting tasksel do the work, with the annoying problem
13100 of not getting any feedback at all when something fails (like a
13101 conffile question from dpkg or a download that fails), using code like
13104 <blockquote
><pre
>
13105 export DEBIAN_FRONTEND=noninteractive
13106 tasksel --new-install
13107 </pre
></blockquote
>
13109 This would invoke tasksel, let its automatic task selection pick the
13110 tasks to install, and continue to install the requested tasks without
13111 any output what so ever.
13113 Recently I revisited this problem while working on the automatic
13114 package upgrade testing, because tasksel would some times hang without
13115 any useful feedback, and I want to see what is going on when it
13116 happen. Then it occured to me, I can parse the output from tasksel
13117 when asked to run in test mode, and use that aptitude command line
13118 printed by tasksel then to simulate the tasksel run. I ended up using
13121 <blockquote
><pre
>
13122 export DEBIAN_FRONTEND=noninteractive
13123 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
13125 </pre
></blockquote
>
13127 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
13128 --without-recommends -o APT::Install-Recommends=no -y install
13129 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
13130 ~pimportant
</tt
>", which will install the gnome desktop task, the
13131 laptop task and all packages with priority standard , required and
13132 important, just like tasksel would have done it during
13133 installation.
</p
>
13135 <p
>A better approach is probably to extend tasksel to be able to
13136 install packages without using debconf-apt-progress, for use cases
13137 like this.
</p
>
13142 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
13143 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
13144 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
13145 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
13146 <description><p
>My
13147 <a href=
"https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
13148 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
13149 finally made the upgrade logs available from
13150 <a href=
"https://people.skolelinux.org/pere/debian-upgrade-testing/
">https://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
13151 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
13152 apt and aptitude, and found their differences interesting. This time
13153 I will only focus on their removal plans.
</p
>
13155 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
13156 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
13157 surprising part is that it want to remove xorg and all
13158 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
13159 sure why. When asking aptitude to do the same, it want to remove
129
13160 packages, but most of them are library packages I suspect are no
13161 longer needed. Both of them want to remove bluetooth packages, which
13162 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
13164 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
13165 which seem like a bad idea and xorg the same way as with Gnome. Asking
13166 aptitude for the same, it wants to remove
192 packages, none which are
13167 too surprising.
</p
>
13169 <p
>I guess the removal of xorg during upgrades should be investigated
13170 and avoided, and perhaps others as well. Here are the complete list
13171 of planned removals. The complete logs is available from the URL
13172 above. Note if you want to repeat these tests, that the upgrade test
13173 for kde+apt-get hung in the tasksel setup because of dpkg asking
13174 conffile questions. No idea why. I worked around it by using
13175 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
13176 continue.
</p
>
13178 <p
><b
>apt-get gnome
72</b
>
13179 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
13180 gnome-desktop-environment gnome-network-admin gtkhtml3.14
13181 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
13182 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
13183 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
13184 serpentine swfdec-mozilla update-manager xorg xserver-xorg
13185 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
13186 xserver-xorg-input-kbd xserver-xorg-input-mouse
13187 xserver-xorg-input-synaptics xserver-xorg-input-wacom
13188 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
13189 xserver-xorg-video-ati xserver-xorg-video-chips
13190 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
13191 xserver-xorg-video-dummy xserver-xorg-video-fbdev
13192 xserver-xorg-video-glint xserver-xorg-video-i128
13193 xserver-xorg-video-i740 xserver-xorg-video-imstt
13194 xserver-xorg-video-intel xserver-xorg-video-mach64
13195 xserver-xorg-video-mga xserver-xorg-video-neomagic
13196 xserver-xorg-video-nsc xserver-xorg-video-nv
13197 xserver-xorg-video-openchrome xserver-xorg-video-r128
13198 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
13199 xserver-xorg-video-rendition xserver-xorg-video-s3
13200 xserver-xorg-video-s3virge xserver-xorg-video-savage
13201 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
13202 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
13203 xserver-xorg-video-tga xserver-xorg-video-trident
13204 xserver-xorg-video-tseng xserver-xorg-video-v4l
13205 xserver-xorg-video-vesa xserver-xorg-video-vga
13206 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
13207 xulrunner-
1.9-gnome-support
</p
>
13209 <p
><b
>aptitude gnome
129</b
>
13211 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
13212 djvulibre-desktop finger gnome-app-install gnome-mount
13213 gnome-network-admin gnome-spell gnome-vfs-obexftp
13214 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
13215 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
13216 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
13217 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
13218 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
13219 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
13220 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
13221 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
13222 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
13223 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
13224 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
13225 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
13226 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
13227 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
13228 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
13229 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
13230 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
13231 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
13232 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
13233 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
13234 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
13235 openoffice.org-writer2latex openssl-blacklist p7zip
13236 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
13237 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
13238 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
13239 swfdec-mozilla totem-gstreamer update-manager wodim
13240 xserver-xorg-video-cyrix xserver-xorg-video-imstt
13241 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
13244 <p
><b
>apt-get kde
82</b
>
13246 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
13247 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
13248 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
13249 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
13250 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
13251 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
13252 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
13253 xserver-xorg-input-kbd xserver-xorg-input-mouse
13254 xserver-xorg-input-synaptics xserver-xorg-input-wacom
13255 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
13256 xserver-xorg-video-ati xserver-xorg-video-chips
13257 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
13258 xserver-xorg-video-dummy xserver-xorg-video-fbdev
13259 xserver-xorg-video-glint xserver-xorg-video-i128
13260 xserver-xorg-video-i740 xserver-xorg-video-imstt
13261 xserver-xorg-video-intel xserver-xorg-video-mach64
13262 xserver-xorg-video-mga xserver-xorg-video-neomagic
13263 xserver-xorg-video-nsc xserver-xorg-video-nv
13264 xserver-xorg-video-openchrome xserver-xorg-video-r128
13265 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
13266 xserver-xorg-video-rendition xserver-xorg-video-s3
13267 xserver-xorg-video-s3virge xserver-xorg-video-savage
13268 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
13269 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
13270 xserver-xorg-video-tga xserver-xorg-video-trident
13271 xserver-xorg-video-tseng xserver-xorg-video-v4l
13272 xserver-xorg-video-vesa xserver-xorg-video-vga
13273 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
13275 <p
><b
>aptitude kde
192</b
>
13276 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
13277 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
13278 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
13279 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
13280 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
13281 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
13282 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
13283 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
13284 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
13285 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
13286 kghostview khelpcenter khexedit kiconedit kitchensync klatin
13287 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
13288 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
13289 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
13290 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
13291 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
13292 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
13293 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
13294 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
13295 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
13296 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
13297 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
13298 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
13299 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
13300 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
13301 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
13302 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
13303 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
13304 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
13305 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
13306 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
13307 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
13308 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
13309 texlive-common texlive-doc-base texlive-fonts-recommended
13310 xserver-xorg-video-cyrix xserver-xorg-video-imstt
13311 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
13312 xulrunner-
1.9</p
>
13318 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
13319 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
13320 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
13321 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
13322 <description><p
>The last few days I have done some upgrade testing in Debian, to
13323 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
13324 have been discovered and reported in the process
13325 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
13326 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
13327 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
13328 kdebase-workspace-data), and to get a more regular testing going on, I
13329 am working on a script to automate the test.
</p
>
13331 <p
>The idea is to create a Lenny chroot and use tasksel to install a
13332 Gnome or KDE desktop installation inside the chroot before upgrading
13333 it. To ensure no services are started in the chroot, a policy-rc.d
13334 script is inserted. To make sure tasksel believe it is to install a
13335 desktop on a laptop, the tasksel tests are replaced in the chroot
13336 (only acceptable because this is a throw-away chroot).
</p
>
13338 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
13339 currently always fail because udev refuses to upgrade with the kernel
13340 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
13341 is created. The bug report
13342 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
13343 this problem do not trigger in a chroot, but I touch the file anyway
13344 to make sure the upgrade go well. Testing on virtual and real
13345 hardware have failed me because of udev so far, and creating this file
13346 do the trick in such settings anyway. This is a
13347 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
13348 issue
</a
> and the current udev behaviour is intended by the udev
13349 maintainer because he lack the resources to rewrite udev to keep
13350 working with old kernels or something like that. I really wish the
13351 udev upstream would keep udev backwards compatible, to avoid such
13352 upgrade problem, but given that they fail to do so, I guess
13353 documenting the way out of this mess is the best option we got for
13354 Debian Squeeze.
</p
>
13356 <p
>Anyway, back to the task at hand, testing upgrades. This test
13357 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
13360 <blockquote
><pre
>
13364 if [
"$
1" ] ; then
13373 exec
&lt; /dev/null
13375 mirror=http://ftp.skolelinux.org/debian
13376 tmpdir=chroot-$from-upgrade-$to-$desktop
13378 debootstrap $from $tmpdir $mirror
13379 chroot $tmpdir aptitude update
13380 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
13384 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
13386 umount $tmpdir/proc
13388 mount -t proc proc $tmpdir/proc
13389 # Make sure proc is unmounted also on failure
13390 trap exit_cleanup EXIT INT
13392 chroot $tmpdir aptitude -y install debconf-utils
13394 # Make sure tasksel autoselection trigger. It need the test scripts
13395 # to return the correct answers.
13396 echo tasksel tasksel/desktop multiselect $desktop | \
13397 chroot $tmpdir debconf-set-selections
13399 # Include the desktop and laptop task
13400 for test in desktop laptop ; do
13401 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
13405 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
13408 DEBIAN_FRONTEND=noninteractive
13409 DEBIAN_PRIORITY=critical
13410 export DEBIAN_FRONTEND DEBIAN_PRIORITY
13411 chroot $tmpdir tasksel --new-install
13413 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
13414 chroot $tmpdir aptitude update
13415 touch $tmpdir/etc/udev/kernel-upgrade
13416 chroot $tmpdir aptitude -y dist-upgrade
13418 </pre
></blockquote
>
13420 <p
>I suspect it would be useful to test upgrades with both apt-get and
13421 with aptitude, but I have not had time to look at how they behave
13422 differently so far. I hope to get a cron job running to do the test
13423 regularly and post the result on the web. The Gnome upgrade currently
13424 work, while the KDE upgrade fail because of the bug in
13425 kdebase-workspace-data
</p
>
13427 <p
>I am not quite sure what kind of extract from the huge upgrade logs
13428 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
13429 post, so I will refrain from trying. I can report that for Gnome,
13430 aptitude report
760 packages upgraded,
448 newly installed,
129 to
13431 remove and
1 not upgraded and
1024MB need to be downloaded while for
13432 KDE the same numbers are
702 packages upgraded,
507 newly installed,
13433 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
13435 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
13436 is able to migrate to dependency based boot sequencing and parallel
13437 booting without a hitch. Was unsure if there were still bugs with
13438 packages failing to clean up their obsolete init.d script during
13439 upgrades, and no such problem seem to affect the Gnome desktop+laptop
13440 packages.
</p
>
13445 <title>Upstart or sysvinit - as init.d scripts see it
</title>
13446 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
13447 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
13448 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
13449 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
13450 scripts to migrate (some of) their operations to upstart job while
13451 keeping the init.d for hurd and kfreebsd. The packages with such
13452 needs will need a way to get their init.d scripts to behave
13453 differently when used with sysvinit and with upstart. Because of
13454 this, I had a look at the environment variables set when a init.d
13455 script is running under upstart, and when it is not.
</p
>
13457 <p
>With upstart, I notice these environment variables are set when a
13458 script is started from rcS.d/ (ignoring some irrelevant ones like
13459 COLUMNS):
</p
>
13461 <blockquote
><pre
>
13467 UPSTART_EVENTS=startup
13469 UPSTART_JOB=rc-sysinit
13470 </pre
></blockquote
>
13472 <p
>With sysvinit, these environment variables are set for the same
13475 <blockquote
><pre
>
13476 INIT_VERSION=sysvinit-
2.88
13481 </pre
></blockquote
>
13483 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
13484 sysvinit are not set by upstart. Not sure if it is intentional or not
13485 to not be compatible with sysvinit in this regard.
</p
>
13487 <p
>For scripts needing to behave differently when upstart is used,
13488 looking for the UPSTART_JOB environment variable seem to be a good
13494 <title>A manual for standards wars...
</title>
13495 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
13496 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
13497 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
13498 <description><p
>Via the
13499 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
13500 of Rob Weir
</a
> I came across the very interesting essay named
13501 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
13502 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
13503 following the standards wars of today.
</p
>
13508 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
13509 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
13510 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
13511 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
13512 <description><p
>When using sitesummary at a site to track machines, it is possible
13513 to get a list of the machine types in use thanks to the DMI
13514 information extracted from each machine. The script to do so is
13515 included in the sitesummary package, and here is example output from
13516 the Skolelinux build servers:
</p
>
13518 <blockquote
><pre
>
13519 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
13521 Dell Computer Corporation
1
13524 eserver xSeries
345 -[
8670M1X]-
1
13528 </pre
></blockquote
>
13530 <p
>The quality of the report depend on the quality of the DMI tables
13531 provided in each machine. Here there are Intel machines without model
13532 information listed with Intel as vendor and no model, and virtual Xen
13533 machines listed as [no-dmi-info]. One can add -l as a command line
13534 option to list the individual machines.
</p
>
13536 <p
>A larger list is
13537 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
13538 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
13539 provide the basic sitesummary report publicly. In their report there
13540 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
13541 their machines, and as sitesummary is available in both distributions,
13542 it is trivial to get all of them to report to the same central
13543 collector.
</p
>
13548 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
13549 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
13550 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</guid>
13551 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
13552 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
13553 start at boot when an NVidia video card is used is handled. The
13554 problem seem to be that the nvidia X.org driver uses a long time to
13555 initialize, and this duration is longer than kdm is configured to
13558 <p
>I came across two bugs related to this issue,
13559 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
13560 against initscripts and passed on to nvidia-glx when it became obvious
13561 that the nvidia drivers were involved, and
13562 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
13563 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
13565 <p
>To me, it seem that no-one is interested in actually solving the
13566 problem nvidia video card owners experience and make sure the Debian
13567 distribution work out of the box for these users. The nvidia driver
13568 maintainers expect kdm to be set up to wait longer, while kdm expect
13569 the nvidia driver maintainers to fix the driver to start faster, and
13570 while they wait for each other I guess the users end up switching to a
13571 distribution that work for them. I have no idea what the solution is,
13572 but I am pretty sure that waiting for each other is not it.
</p
>
13574 <p
>I wonder why we end up handling bugs this way.
</p
>
13579 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
13580 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
13581 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
13582 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
13583 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
13584 The feature seem to hold up pretty well, but three fairly serious
13585 issues are known and should be solved:
13587 <p
><ul
>
13589 <li
>The wicd package seen to
13590 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
13591 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
13592 parallel booting is enabled. No idea why, but the wicd maintainer
13593 seem to be on the case.
</li
>
13595 <li
>The nvidia X driver seem to
13596 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
13597 triggered more easily when parallel booting is in effect. The
13598 maintainer is on the case.
</li
>
13600 <li
>The sysv-rc package fail to properly enable dependency based boot
13601 sequencing (the shutdown is broken) when old file-rc users
13602 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
13603 sysv-rc. One way to solve it would be for file-rc to create
13604 /etc/init.d/.legacy-bootordering, and another is to try to make
13605 sysv-rc more robust. Will investigate some more and probably upload a
13606 workaround in sysv-rc to help those trying to move from file-rc to
13607 sysv-rc get a working shutdown.
</li
>
13609 </ul
></p
>
13611 <p
>All in all not many surprising issues, and all of them seem
13612 solvable before Squeeze is released. In addition to these there are
13613 some packages with bugs in their dependencies and run level settings,
13614 which I expect will be fixed in a reasonable time span.
</p
>
13616 <p
>If you report any problems with dependencies in init.d scripts to
13617 the BTS, please usertag the report to get it to show up at
13618 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13619 list of usertagged bugs related to this
</a
>.
</p
>
13621 <p
>Update: Correct bug number to file-rc issue.
</p
>
13626 <title>More flexible firmware handling in debian-installer
</title>
13627 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
13628 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
13629 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
13630 <description><p
>After a long break from debian-installer development, I finally
13631 found time today to return to the project. Having to spend less time
13632 working dependency based boot in debian, as it is almost complete now,
13633 definitely helped freeing some time.
</p
>
13635 <p
>A while back, I ran into a problem while working on Debian Edu. We
13636 include some firmware packages on the Debian Edu CDs, those needed to
13637 get disk and network controllers working. Without having these
13638 firmware packages available during installation, it is impossible to
13639 install Debian Edu on the given machine, and because our target group
13640 are non-technical people, asking them to provide firmware packages on
13641 an external medium is a support pain. Initially, I expected it to be
13642 enough to include the firmware packages on the CD to get
13643 debian-installer to find and use them. This proved to be wrong.
13644 Next, I hoped it was enough to symlink the relevant firmware packages
13645 to some useful location on the CD (tried /cdrom/ and
13646 /cdrom/firmware/). This also proved to not work, and at this point I
13647 found time to look at the debian-installer code to figure out what was
13648 going to work.
</p
>
13650 <p
>The firmware loading code is in the hw-detect package, and a closer
13651 look revealed that it would only look for firmware packages outside
13652 the installation media, so the CD was never checked for firmware
13653 packages. It would only check USB sticks, floppies and other
13654 "external
" media devices. Today I changed it to also look in the
13655 /cdrom/firmware/ directory on the mounted CD or DVD, which should
13656 solve the problem I ran into with Debian edu. I also changed it to
13657 look in /firmware/, to make sure the installer also find firmware
13658 provided in the initrd when booting the installer via PXE, to allow us
13659 to provide the same feature in the PXE setup included in Debian
13662 <p
>To make sure firmware deb packages with a license questions are not
13663 activated without asking if the license is accepted, I extended
13664 hw-detect to look for preinst scripts in the firmware packages, and
13665 run these before activating the firmware during installation. The
13666 license question is asked using debconf in the preinst, so this should
13667 solve the issue for the firmware packages I have looked at so far.
</p
>
13669 <p
>If you want to discuss the details of these features, please
13670 contact us on debian-boot@lists.debian.org.
</p
>
13675 <title>Parallellized boot is now the default in Debian/unstable
</title>
13676 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
13677 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
13678 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
13679 <description><p
>Since this evening, parallel booting is the default in
13680 Debian/unstable for machines using dependency based boot sequencing.
13681 Apparently the testing of concurrent booting has been wider than
13682 expected, if I am to believe the
13683 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
13684 on debian-devel@
</a
>, and I concluded a few days ago to move forward
13685 with the feature this weekend, to give us some time to detect any
13686 remaining problems before Squeeze is frozen. If serious problems are
13687 detected, it is simple to change the default back to sequential boot.
13688 The upload of the new sysvinit package also activate a new upstream
13691 More information about
13692 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13693 based boot sequencing
</a
> is available from the Debian wiki. It is
13694 currently possible to disable parallel booting when one run into
13695 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
13697 <blockquote
><pre
>
13699 </pre
></blockquote
>
13701 <p
>If you report any problems with dependencies in init.d scripts to
13702 the BTS, please usertag the report to get it to show up at
13703 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13704 list of usertagged bugs related to this
</a
>.
</p
>
13709 <title>Sitesummary tip: Listing MAC address of all clients
</title>
13710 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
13711 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
13712 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
13713 <description><p
>In the recent Debian Edu versions, the
13714 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
13715 system
</a
> is used to keep track of the machines in the school
13716 network. Each machine will automatically report its status to the
13717 central server after boot and once per night. The network setup is
13718 also reported, and using this information it is possible to get the
13719 MAC address of all network interfaces in the machines. This is useful
13720 to update the DHCP configuration.
</p
>
13722 <p
>To give some idea how to use sitesummary, here is a one-liner to
13723 ist all MAC addresses of all machines reporting to sitesummary. Run
13724 this on the collector host:
</p
>
13726 <blockquote
><pre
>
13727 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
13728 </pre
></blockquote
>
13730 <p
>This will list all MAC addresses assosiated with all machine, one
13731 line per machine and with space between the MAC addresses.
</p
>
13733 <p
>To allow system administrators easier job at adding static DHCP
13734 addresses for hosts, it would be possible to extend this to fetch
13735 machine information from sitesummary and update the DHCP and DNS
13736 tables in LDAP using this information. Such tool is unfortunately not
13737 written yet.
</p
>
13742 <title>systemd, an interesting alternative to upstart
</title>
13743 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
13744 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
13745 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
13746 <description><p
>The last few days a new boot system called
13747 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
13749 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
13751 to the free software world. I have not yet had time to play around
13752 with it, but it seem to be a very interesting alternative to
13753 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
13754 a good alternative for Debian when we are able to switch to an event
13755 based boot system. Tollef is
13756 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
13757 systemd into Debian, and I look forward to seeing how well it work. I
13758 like the fact that systemd handles init.d scripts with dependency
13759 information natively, allowing them to run in parallel where upstart
13760 at the moment do not.
</p
>
13762 <p
>Unfortunately do systemd have the same problem as upstart regarding
13763 platform support. It only work on recent Linux kernels, and also need
13764 some new kernel features enabled to function properly. This means
13765 kFreeBSD and Hurd ports of Debian will need a port or a different boot
13766 system. Not sure how that will be handled if systemd proves to be the
13767 way forward.
</p
>
13769 <p
>In the mean time, based on the
13770 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
13771 on debian-devel@
</a
> regarding parallel booting in Debian, I have
13772 decided to enable full parallel booting as the default in Debian as
13773 soon as possible (probably this weekend or early next week), to see if
13774 there are any remaining serious bugs in the init.d dependencies. A
13775 new version of the sysvinit package implementing this change is
13776 already in experimental. If all go well, Squeeze will be released
13777 with parallel booting enabled by default.
</p
>
13782 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
13783 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
13784 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
13785 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
13786 <description><p
>These days, the init.d script dependencies in Squeeze are quite
13787 complete, so complete that it is actually possible to run all the
13788 init.d scripts in parallell based on these dependencies. If you want
13789 to test your Squeeze system, make sure
13790 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13791 based boot sequencing
</a
> is enabled, and add this line to
13792 /etc/default/rcS:
</p
>
13794 <blockquote
><pre
>
13795 CONCURRENCY=makefile
13796 </pre
></blockquote
>
13798 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
13799 scripts in parallel using the dependency information stored in
13800 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
13801 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
13802 to try to start the kdm and gdm scripts as early as possible, and will
13803 start the facilities required by kdm or gdm as early as possible to
13804 make this happen.
</p
>
13806 <p
>Give it a try, and see if you like the result. If some services
13807 fail to start properly, it is most likely because they have incomplete
13808 init.d script dependencies in their startup script (or some of their
13809 dependent scripts have incomplete dependencies). Report bugs and get
13810 the package maintainers to fix it. :)
</p
>
13812 <p
>Running scripts in parallel could be the default in Debian when we
13813 manage to get the init.d script dependencies complete and correct. I
13814 expect we will get there in Squeeze+
1, if we get manage to test and
13815 fix the remaining issues.
</p
>
13817 <p
>If you report any problems with dependencies in init.d scripts to
13818 the BTS, please usertag the report to get it to show up at
13819 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13820 list of usertagged bugs related to this
</a
>.
</p
>
13825 <title>Debian has switched to dependency based boot sequencing
</title>
13826 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
13827 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
13828 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
13829 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
13830 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
13831 have been migrated to using dependency based boot sequencing. This
13832 conclude work me and others have been doing for the last three days.
13833 It feels great to see this finally part of the default Debian
13834 installation. Now we just need to weed out the last few problems that
13835 are bound to show up, to get everything ready for Squeeze.
</p
>
13837 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
13838 fixing the more fundamental problem of handing the event based
13839 non-predictable kernel in the early boot.
</p
>
13844 <title>Taking over sysvinit development
</title>
13845 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
13846 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
13847 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
13848 <description><p
>After several years of frustration with the lack of activity from
13849 the existing sysvinit upstream developer, I decided a few weeks ago to
13850 take over the package and become the new upstream. The number of
13851 patches to track for the Debian package was becoming a burden, and the
13852 lack of synchronization between the distribution made it hard to keep
13853 the package up to date.
</p
>
13855 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
13856 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
13857 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
13858 and Fedora), based on the patches currently in use in these
13859 distributions. We Debian maintainers plan to move to this tarball as
13860 the new upstream as soon as we find time to do the merge. Since the
13861 new tarball was created, we agreed with Werner at SuSe to make a new
13862 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
13863 development there. The project is registered and currently waiting
13864 for approval by the Savannah administrators, and as soon as it is
13865 approved, we will import the old versions from svn and continue
13866 working on the future release.
</p
>
13868 <p
>It is a bit ironic that this is done now, when some of the involved
13869 distributions are moving to upstart as a syvinit replacement.
</p
>
13874 <title>Debian boots quicker and quicker
</title>
13875 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
13876 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
13877 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
13878 <description><p
>I spent Monday and tuesday this week in London with a lot of the
13879 people involved in the boot system on Debian and Ubuntu, to see if we
13880 could find more ways to speed up the boot system. This was an Ubuntu
13882 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
13883 gathering
</a
>. It was quite productive. We also discussed the future
13884 of boot systems, and ways to handle the increasing number of boot
13885 issues introduced by the Linux kernel becoming more and more
13886 asynchronous and event base. The Ubuntu approach using udev and
13887 upstart might be a good way forward. Time will show.
</p
>
13889 <p
>Anyway, there are a few ways at the moment to speed up the boot
13890 process in Debian. All of these should be applied to get a quick
13895 <li
>Use dash as /bin/sh.
</li
>
13897 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
13898 clock is in UTC.
</li
>
13900 <li
>Install and activate the insserv package to enable
13901 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13902 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
13906 These points are based on the Google summer of code work done by
13907 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
13908 Villegas
</a
>.
13910 <p
>Support for makefile-style concurrency during boot was uploaded to
13911 unstable yesterday. When we tested it, we were able to cut
6 seconds
13912 from the boot sequence. It depend on very correct dependency
13913 declaration in all init.d scripts, so I expect us to find edge cases
13914 where the dependences in some scripts are slightly wrong when we start
13915 using this.
</p
>
13917 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
13918 introduced by Raphael Geissert today, one that could affect the
13919 startup speed as well. Instead of starting some scripts concurrently
13920 from rcS.d/ and another set of scripts from rc2.d/, it would be
13921 possible to run a of them in the same process. A quick way to test
13922 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
13923 insserv
'. Will need to test if that work. :)
</p
>
13928 <title>BSAs påstander om piratkopiering møter motstand
</title>
13929 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
13930 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
13931 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
13932 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
13933 programvareselskapene som Microsoft og Apple, publisert en rapport der
13934 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
13935 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
13937 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
13938 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
13939 dagene. Et spesielt interessant kommentar fra Sverige,
13940 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
13941 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
13944 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
13945 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
13946 företag.
"Man bör nog kanske inte se de här siffrorna som helt
13947 exakta
", säger BSAs Sverigechef John Hugosson.
13948 </blockquote
>
13950 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
13951 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
13952 piracy figures need a shot of reality
</a
> og
<a
13953 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
13954 Copyright Treaty Work?
</a
></p
>
13956 <p
>Fant lenkene via
<a
13957 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
13958 på Slashdot
</a
>.
</p
>
13963 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
13964 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
13965 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
13966 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
13967 <description><p
>Kom over
13968 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
13969 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
13970 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
13971 jobber til daglig. En rask opptelling forteller meg at vi har
490
13972 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
13973 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
13974 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
13979 <title>Kryptert harddisk - naturligvis
</title>
13980 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
13981 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
13982 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
13983 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
13984 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
13985 når en tar tap av arbeidstid, fortrolige dokumenter,
13986 personopplysninger og alt annet det innebærer. Det er ingen tvil om
13987 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
13988 til at jeg har kryptert harddisken på både kontormaskinen og min
13989 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13990 komme på avveie, den første informasjon relatert til jobben min ved
13991 Universitetet i Oslo, og den andre relatert til blant annet
13992 foreningsarbeide. Kryptering av diskene gjør at det er lite
13993 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13994 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13995 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13996 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13997 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13998 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13999 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
14000 det er gjort slik jeg gjør det er minimale, og gevinstene er
14001 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
14002 maskinen reinstalleres og alt er tapt.
</p
>
14004 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
14005 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
14006 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
14007 er for min del høyere enn gevinsten. Jeg tror oddsene for at
14008 f.eks. etteretningsorganisasjoner har glede av å titte på mine
14009 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
14010 gjøre det vanskeligere for angripere med kompetanse og ressurser er
14011 betydelige.
</p
>
14016 <title>Two projects that have improved the quality of free software a lot
</title>
14017 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
14018 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
14019 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
14020 <description><p
>There are two software projects that have had huge influence on the
14021 quality of free software, and I wanted to mention both in case someone
14022 do not yet know them.
</p
>
14024 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
14025 tool to detect and expose errors in the memory handling of programs.
14026 It is easy to use, all one need to do is to run
'valgrind program
',
14027 and it will report any problems on stdout. It is even better if the
14028 program include debug information. With debug information, it is able
14029 to report the source file name and line number where the problem
14030 occurs. It can report things like
'reading past memory block in file
14031 X line N, the memory block was allocated in file Y, line M
', and
14032 'using uninitialised value in control logic
'. This tool has made it
14033 trivial to investigate reproducible crash bugs in programs, and have
14034 reduced the number of this kind of bugs in free software a lot.
14036 <p
>The second one is
14037 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
14038 a source code checker. It is able to process the source of a program
14039 and find problems in the logic without running the program. It
14040 started out as the Stanford Checker and became well known when it was
14041 used to find bugs in the Linux kernel. It is now a commercial tool
14042 and the company behind it is running
14043 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
14044 free software community, where a lot of free software projects get
14045 their source checked for free. Several thousand defects have been
14046 found and fixed so far. It can find errors like
'lock L taken in file
14047 X line N is never released if exiting in line M
', or
'the code in file
14048 Y lines O to P can never be executed
'. The projects included in the
14049 community service project have managed to get rid of a lot of
14050 reliability problems thanks to Coverity.
</p
>
14052 <p
>I believe tools like this, that are able to automatically find
14053 errors in the source, are vital to improve the quality of software and
14054 make sure we can get rid of the crashing and failing software we are
14055 surrounded by today.
</p
>
14060 <title>No patch is not better than a useless patch
</title>
14061 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
14062 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
14063 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
14064 <description><p
>Julien Blache
14065 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
14066 patch is better than a useless patch
</a
>. I completely disagree, as a
14067 patch allow one to discuss a concrete and proposed solution, and also
14068 prove that the issue at hand is important enough for someone to spent
14069 time on fixing it. No patch do not provide any of these positive
14070 properties.
</p
>
14075 <title>Standardize on protocols and formats, not vendors and applications
</title>
14076 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
14077 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
14078 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
14079 <description><p
>Where I work at the University of Oslo, one decision stand out as a
14080 very good one to form a long lived computer infrastructure. It is the
14081 simple one, lost by many in todays computer industry: Standardize on
14082 open network protocols and open exchange/storage formats, not applications.
14083 Applications come and go, while protocols and files tend to stay, and
14084 thus one want to make it easy to change application and vendor, while
14085 avoiding conversion costs and locking users to a specific platform or
14086 application.
</p
>
14088 <p
>This approach make it possible to replace the client applications
14089 independently of the server applications. One can even allow users to
14090 use several different applications as long as they handle the selected
14091 protocol and format. In the normal case, only one client application
14092 is recommended and users only get help if they choose to use this
14093 application, but those that want to deviate from the easy path are not
14094 blocked from doing so.
</p
>
14096 <p
>It also allow us to replace the server side without forcing the
14097 users to replace their applications, and thus allow us to select the
14098 best server implementation at any moment, when scale and resouce
14099 requirements change.
</p
>
14101 <p
>I strongly recommend standardizing - on open network protocols and
14102 open formats, but I would never recommend standardizing on a single
14103 application that do not use open network protocol or open formats.
</p
>
14108 <title>Returning from Skolelinux developer gathering
</title>
14109 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
14110 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
14111 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
14112 <description><p
>I
'm sitting on the train going home from this weekends Debian
14113 Edu/Skolelinux development gathering. I got a bit done tuning the
14114 desktop, and looked into the dynamic service location protocol
14115 implementation avahi. It look like it could be useful for us. Almost
14116 30 people participated, and I believe it was a great environment to
14117 get to know the Skolelinux system. Walter Bender, involved in the
14118 development of the Sugar educational platform, presented his stuff and
14119 also helped me improve my OLPC installation. He also showed me that
14120 his Turtle Art application can be used in standalone mode, and we
14121 agreed that I would help getting it packaged for Debian. As a
14122 standalone application it would be great for Debian Edu. We also
14123 tried to get the video conferencing working with two OLPCs, but that
14124 proved to be too hard for us. The application seem to need more work
14125 before it is ready for me. I look forward to getting home and relax
14131 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
14132 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
14133 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
14134 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
14135 <description><p
>The state of standardized LDAP schemas on Linux is far from
14136 optimal. There is RFC
2307 documenting one way to store NIS maps in
14137 LDAP, and a modified version of this normally called RFC
2307bis, with
14138 some modifications to be compatible with Active Directory. The RFC
14139 specification handle the content of a lot of system databases, but do
14140 not handle DNS zones and DHCP configuration.
</p
>
14142 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
14143 we would like to store information about users, SMB clients/hosts,
14144 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
14145 and LTSP configuration in LDAP. These objects have a lot in common,
14146 but with the current LDAP schemas it is not possible to have one
14147 object per entity. For example, one need to have at least three LDAP
14148 objects for a given computer, one with the SMB related stuff, one with
14149 DNS information and another with DHCP information. The schemas
14150 provided for DNS and DHCP are impossible to combine into one LDAP
14151 object. In addition, it is impossible to implement quick queries for
14152 netgroup membership, because of the way NIS triples are implemented.
14153 It just do not scale. I believe it is time for a few RFC
14154 specifications to cleam up this mess.
</p
>
14156 <p
>I would like to have one LDAP object representing each computer in
14157 the network, and this object can then keep the SMB (ie host key), DHCP
14158 (mac address/name) and DNS (name/IP address) settings in one place.
14159 It need to be efficently stored to make sure it scale well.
</p
>
14161 <p
>I would also like to have a quick way to map from a user or
14162 computer and to the net group this user or computer is a member.
</p
>
14164 <p
>Active Directory have done a better job than unix heads like myself
14165 in this regard, and the unix side need to catch up. Time to start a
14166 new IETF work group?
</p
>
14171 <title>Endelig er Debian Lenny gitt ut
</title>
14172 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
14173 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
14174 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
14175 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
14176 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
14177 Et langt steg videre for Debian-prosjektet, og en rekke nye
14178 programpakker blir nå tilgjengelig for de av oss som bruker den
14179 stabile utgaven av Debian. Neste steg er nå å få
14180 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
14181 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
14182 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
14183 slippes løs på skolene. Takk til alle debian-utviklerne som har
14184 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
14185 bootsekvens tilgjengelig i stabil utgave, vha pakken
14186 <tt
>insserv
</tt
>.
</p
>
14191 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
14192 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
14193 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
14194 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
14195 <description><p
>This weekend we had a small developer gathering for Debian Edu in
14196 Oslo. Most of Saturday was used for the general assemly for the
14197 member organization, but the rest of the weekend I used to tune the
14198 LTSP installation. LTSP now work out of the box on the
10-network.
14199 Acer Aspire One proved to be a very nice thin client, with both
14200 screen, mouse and keybard in a small box. Was working on getting the
14201 diskless workstation setup configured out of the box, but did not
14202 finish it before the weekend was up.
</p
>
14204 <p
>Did not find time to look at the
4 VGA cards in one box we got from
14205 the Brazilian group, so that will have to wait for the next
14206 development gathering. Would love to have the Debian Edu installer
14207 automatically detect and configure a multiseat setup when it find one
14208 of these cards.
</p
>
14213 <title>The sorry state of multimedia browser plugins in Debian
</title>
14214 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
14215 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
14216 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
14217 <description><p
>Recently I have spent some time evaluating the multimedia browser
14218 plugins available in Debian Lenny, to see which one we should use by
14219 default in Debian Edu. We need an embedded video playing plugin with
14220 control buttons to pause or stop the video, and capable of streaming
14221 all the multimedia content available on the web. The test results and
14222 notes are available on
14223 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
14224 Debian wiki
</a
>. I was surprised how few of the plugins are able to
14225 fill this need. My personal video player favorite, VLC, has a really
14226 bad plugin which fail on a lot of the test pages. A lot of the MIME
14227 types I would expect to work with any free software player (like
14228 video/ogg), just do not work. And simple formats like the
14229 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
14230 totem and vlc plugins. I hope the situation will improve soon. No
14231 wonder sites use the proprietary Adobe flash to play video.
</p
>
14233 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
14234 be the only one fitting our needs. :/
</p
>