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>45 orphaned Debian packages moved to git,
391 to go
</title>
11 <link>https://people.skolelinux.org/pere/blog/
45_orphaned_Debian_packages_moved_to_git__391_to_go.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/
45_orphaned_Debian_packages_moved_to_git__391_to_go.html
</guid>
13 <pubDate>Thu,
25 Apr
2024 22:
00:
00 +
0200</pubDate>
14 <description><p
>Nine days ago, I started migrating orphaned Debian packages with no
15 version control system listed in debian/control of the source to git.
16 At the time there were
438 such packages. Now there are
391,
17 according to the UDD. In reality it is slightly less, as there is a
18 delay between uploads and UDD updates. In the nine days since, I have
19 thus been able to work my way through ten percent of the packages. I
20 am starting to run out of steam, and hope someone else will also help
21 brushing some dust of these packages. Here is a recipe how to do it.
23 I start by picking a random package by querying the UDD for a list of
24 10 random packages from the set of remaining packages:
26 <blockquote
><pre
>
27 PGPASSWORD=
"udd-mirror
" psql --port=
5432 --host=udd-mirror.debian.net \
28 --username=udd-mirror udd -c
"select source from sources \
29 where release =
'sid
' and (vcs_url ilike
'%anonscm.debian.org%
' \
30 OR vcs_browser ilike
'%anonscm.debian.org%
' or vcs_url IS NULL \
31 OR vcs_browser IS NULL) AND maintainer ilike
'%packages@qa.debian.org%
' \
32 order by random() limit
10;
"
33 </pre
></blockquote
>
35 <p
>Next, I visit http://salsa.debian.org/debian and search for the
36 package name, to ensure no git repository already exist. If it does,
37 I clone it and try to get it to an uploadable state, and add the Vcs-*
38 entries in d/control to make the repository more widely known. These
39 packages are a minority, so I will not cover that use case here.
</p
>
41 <p
>For packages without an existing git repository, I run the
42 following script
<tt
>debian-snap-to-salsa
</tt
> to prepare a git
43 repository with the existing packaging.
</p
>
45 <blockquote
><pre
>
48 # See also https://bugs.debian.org/
804722#
31
52 # Move to this Standards-Version.
57 if [ -z
"$PKG
" ]; then
58 echo
"usage: $
0 <pkgname
>"
62 if [ -e
"${PKG}-salsa
" ]; then
63 echo
"error: ${PKG}-salsa already exist, aborting.
"
67 if [ -z
"ALLOWFAILURE
" ] ; then
71 # Fetch every snapshotted source package. Manually loop until all
72 # transfers succeed, as
'gbp import-dscs --debsnap
' do not fail on
74 until debsnap --force -v $PKG || $ALLOWFAILURE ; do sleep
1; done
75 mkdir ${PKG}-salsa; cd ${PKG}-salsa
78 # Specify branches to override any debian/gbp.conf file present in the
80 gbp import-dscs --debian-branch=master --upstream-branch=upstream \
81 --pristine-tar ../source-$PKG/*.dsc
83 # Add Vcs pointing to Salsa Debian project (must be manually created
85 if ! grep -q ^Vcs- debian/control ; then
86 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
87 git commit -m
"Updated vcs in d/control to Salsa.
" debian/control
90 # Tell gbp to enforce the use of pristine-tar.
91 inifile +inifile debian/gbp.conf +create +section DEFAULT +key pristine-tar +value True
92 git add debian/gbp.conf
93 git commit -m
"Added d/gbp.conf to enforce the use of pristine-tar.
" debian/gbp.conf
95 # Update to latest Standards-Version.
96 SV=
"$(grep ^Standards-Version: debian/control|awk
'{print $
2}
')
"
97 if [ $SV_LATEST != $SV ]; then
98 sed -i
"s/\(Standards-Version: \)\(.*\)/\
1$SV_LATEST/
" debian/control
99 git commit -m
"Updated Standards-Version from $SV to $SV_LATEST.
" debian/control
102 if grep -q pkg-config debian/control; then
103 sed -i s/pkg-config/pkgconf/ debian/control
104 git commit -m
"Replaced obsolete pkg-config build dependency with pkgconf.
" debian/control
107 if grep -q libncurses5-dev debian/control; then
108 sed -i s/libncurses5-dev/libncurses-dev/ debian/control
109 git commit -m
"Replaced obsolete libncurses5-dev build dependency with libncurses-dev.
" debian/control
111 </pre
></blockquote
>
113 Some times the debsnap script fail to download some of the versions.
114 In those cases I investigate, and if I decide the failing versions
115 will not be missed, I call it using ALLOWFAILURE=true to ignore the
116 problem and create the git repository anyway.
</p
>
118 <p
>With the git repository in place, I do a test build (gbp
119 buildpackage) to ensure the build is actually working. If it does not
120 I pick a different package, or if the build failure is trivial to fix,
121 I fix it before continuing. At this stage I revisit
122 http://salsa.debian.org/debian and create the project under this group
123 for the package. I then follow the instructions to publish the local
124 git repository. Here is from a recent example:
</p
>
126 <blockquote
><pre
>
127 git remote add origin git@salsa.debian.org:debian/perl-byacc.git
128 git push --set-upstream origin master upstream pristine-tar
130 </pre
></blockquote
>
132 <p
>With a working build, I have a look at the build rules if I want to
133 remove some more dust. I normally try to move to debhelper compat
134 level
13, which involves removing debian/compat and modifying
135 debian/control to build depend on debhelper-compat (=
13). I also test
136 with
'Rules-Requires-Root: no
' in debian/control and verify in
137 debian/rules that hardening is enabled, and include all of these if
138 the package still build. If it fail to build with level
13, I try
139 with
12,
11,
10 and so on until I find a level where it build, as I do
140 not want to spend a lot of time fixing build issues.
</p
>
142 <p
>Some times, when I feel inspired, I make sure debian/copyright is
143 converted to the machine readable format, often by starting with
144 'debhelper -cc
' and then cleaning up the autogenerated content until
145 it matches realities. If I feel like it, I might also clean up
146 non-dh-based debian/rules files to use the short style dh build
149 <p
>Once I have removed all the dust I care to process for the package,
150 I run
'gbp dch
' to generate a debian/changelog entry based on the
151 commits done so far, run
'dch -r
' to switch from
'UNRELEASED
' to
152 'unstable
' and get an editor to make sure the
'QA upload
' marker is in
153 place and that all long commit descriptions are wrapped into sensible
154 lengths, run
'debcommit --release -a
' to commit and tag the new
155 debian/changelog entry, run
'debuild -S
' to build a source only
156 package, and
'dput ../perl-byacc_2.0-
10_source.changes
' to do the
157 upload. During the entire process, and many times per step, I run
158 'debuild
' to verify the changes done still work. I also some times
159 verify the set of built files using
'find debian
' to see if I can spot
160 any problems (like no file in usr/bin any more or empty package). I
161 also try to fix all lintian issues reported at the end of each
162 'debuild
' run.
</p
>
164 <p
>If I find Debian specific patches, I try to ensure their metadata
165 is fairly up to date and some times I even try to reach out to
166 upstream, to make the upstream project aware of the patches. Most of
167 my emails bounce, so the success rate is low. For projects with no
168 Homepage entry in debian/control I try to track down one, and for
169 packages with no debian/watch file I try to create one. But at least
170 for some of the packages I have been unable to find a functioning
171 upstream, and must skip both of these.
</p
>
173 <p
>If I could handle ten percent in nine days, twenty people could
174 complete the rest in less then five days. I use approximately twenty
175 minutes per package, when I have twenty minutes spare time to spend.
176 Perhaps you got twenty minutes to spare too?
</p
>
178 <p
>As usual, if you use Bitcoin and want to show your support of my
179 activities, please send Bitcoin donations to my address
180 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
182 <p
><strong
>Update
2024-
05-
04:
</strong
> There is
183 <a href=
"https://people.skolelinux.org/pere/blog/images/
2024-
05-
04-debian-snap-to-salsa.sh
">an
184 updated edition of my migration script
</a
>, last updated
185 2024-
04-
05.
</p
>
190 <title>Time to move orphaned Debian packages to git
</title>
191 <link>https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html
</link>
192 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html
</guid>
193 <pubDate>Sun,
14 Apr
2024 09:
30:
00 +
0200</pubDate>
194 <description><p
>There are several packages in Debian without a associated git
195 repository with the packaging history. This is unfortunate and it
196 would be nice if more of these would do so. Quote a lot of these are
197 without a maintainer, ie listed as maintained by the
198 '<a href=
"https://qa.debian.org/developer.php?email=packages%
40qa.debian.org
">Debian
199 QA Group
</a
>' place holder. In fact,
438 packages have this property
200 according to UDD (
<tt
>SELECT source FROM sources WHERE release =
'sid
'
201 AND (vcs_url ilike
'%anonscm.debian.org%
' OR vcs_browser ilike
202 '%anonscm.debian.org%
' or vcs_url IS NULL OR vcs_browser IS NULL) AND
203 maintainer ilike
'%packages@qa.debian.org%
';
</tt
>). Such packages can
204 be updated without much coordination by any Debian developer, as they
205 are considered orphaned.
</p
>
207 <p
>To try to improve the situation and reduce the number of packages
208 without associated git repository, I started a few days ago to search
209 out candiates and provide them with a git repository under the
210 'debian
' collaborative Salsa project. I started with the packages
211 pointing to obsolete Alioth git repositories, and am now working my
212 way across the ones completely without git references. In addition to
213 updating the Vcs-* debian/control fields, I try to update
214 Standards-Version, debhelper compat level, simplify d/rules, switch to
215 Rules-Requires-Root: no and fix lintian issues reported. I only
216 implement those that are trivial to fix, to avoid spending too much
217 time on each orphaned package. So far my experience is that it take
218 aproximately
20 minutes to convert a package without any git
219 references, and a lot more for packages with existing git repositories
220 incompatible with git-buildpackages.
</p
>
222 <p
>So far I have converted
10 packages, and I will keep going until I
223 run out of steam. As should be clear from the numbers, there is
224 enough packages remaining for more people to do the same without
225 stepping on each others toes. I find it useful to start by searching
226 for a git repo already on salsa, as I find that some times a git repo
227 has already been created, but no new version is uploaded to Debian
228 yet. In those cases I start with the existing git repository. I
229 convert to the git-buildpackage+pristine-tar workflow, and ensure a
230 debian/gbp.conf file with
"pristine-tar=True
" is added early, to avoid
231 uploading a orig.tar.gz with the wrong checksum by mistake. Did that
232 three times in the begin before I remembered my mistake.
</p
>
234 <p
>So, if you are a Debian Developer and got some spare time, perhaps
235 considering migrating some orphaned packages to git?
</p
>
237 <p
>As usual, if you use Bitcoin and want to show your support of my
238 activities, please send Bitcoin donations to my address
239 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
244 <title>New and improved sqlcipher in Debian for accessing Signal database
</title>
245 <link>https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html
</link>
246 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html
</guid>
247 <pubDate>Sun,
12 Nov
2023 12:
00:
00 +
0100</pubDate>
248 <description><p
>For a while now I wanted to have direct access to the
249 <a href=
"https://signal.org/
">Signal
</a
> database of messages and
250 channels of my Desktop edition of Signal. I prefer the enforced end
251 to end encryption of Signal these days for my communication with
252 friends and family, to increase the level of safety and privacy as
253 well as raising the cost of the mass surveillance government and
254 non-government entities practice these days. In August I came across
256 <a href=
"https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/
">recipe
257 on how to use sqlcipher to extract statistics from the Signal
258 database
</a
> explaining how to do this. Unfortunately this did not
259 work with the version of sqlcipher in Debian. The
260 <a href=
"http://tracker.debian.org/sqlcipher/
">sqlcipher
</a
>
261 package is a
"fork
" of the sqlite package with added support for
262 encrypted databases. Sadly the current Debian maintainer
263 <a href=
"https://bugs.debian.org/
961598">announced more than three
264 years ago that he did not have time to maintain sqlcipher
</a
>, so it
265 seemed unlikely to be upgraded by the maintainer. I was reluctant to
266 take on the job myself, as I have very limited experience maintaining
267 shared libraries in Debian. After waiting and hoping for a few
268 months, I gave up the last week, and set out to update the package. In
269 the process I orphaned it to make it more obvious for the next person
270 looking at it that the package need proper maintenance.
</p
>
272 <p
>The version in Debian was around five years old, and quite a lot of
273 changes had taken place upstream into the Debian maintenance git
274 repository. After spending a few days importing the new upstream
275 versions, realising that upstream did not care much for SONAME
276 versioning as I saw library symbols being both added and removed with
277 minor version number changes to the project, I concluded that I had to
278 do a SONAME bump of the library package to avoid surprising the
279 reverse dependencies. I even added a simple
280 autopkgtest script to ensure the package work as intended. Dug deep
281 into the hole of learning shared library maintenance, I set out a few
282 days ago to upload the new version to Debian experimental to see what
283 the quality assurance framework in Debian had to say about the result.
284 The feedback told me the pacakge was not too shabby, and yesterday I
285 uploaded the latest version to Debian unstable. It should enter
286 testing today or tomorrow, perhaps delayed by
287 <a href=
"https://bugs.debian.org/
1055812">a small library
288 transition
</a
>.
</p
>
290 <p
>Armed with a new version of sqlcipher, I can now have a look at the
291 SQL database in ~/.config/Signal/sql/db.sqlite. First, one need to
292 fetch the encryption key from the Signal configuration using this
293 simple JSON extraction command:
</p
>
295 <pre
>/usr/bin/jq -r
'.
"key
"' ~/.config/Signal/config.json
</pre
>
297 <p
>Assuming the result from that command is
'secretkey
', which is a
298 hexadecimal number representing the key used to encrypt the database.
299 Next, one can now connect to the database and inject the encryption
300 key for access via SQL to fetch information from the database. Here
301 is an example dumping the database structure:
</p
>
304 % sqlcipher ~/.config/Signal/sql/db.sqlite
305 sqlite
> PRAGMA key =
"x
'secretkey
'";
307 CREATE TABLE sqlite_stat1(tbl,idx,stat);
308 CREATE TABLE conversations(
309 id STRING PRIMARY KEY ASC,
317 , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
318 CREATE TABLE identityKeys(
319 id STRING PRIMARY KEY ASC,
323 id STRING PRIMARY KEY ASC,
326 CREATE TABLE sessions(
330 , ourServiceId STRING, serviceId STRING);
331 CREATE TABLE attachment_downloads(
332 id STRING primary key,
337 CREATE TABLE sticker_packs(
342 coverStickerId INTEGER,
344 downloadAttempts INTEGER,
348 stickerCount INTEGER,
350 , attemptedStatus STRING, position INTEGER DEFAULT
0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
351 INTEGER DEFAULT
0 NOT NULL);
352 CREATE TABLE stickers(
354 packId TEXT NOT NULL,
363 PRIMARY KEY (id, packId),
364 CONSTRAINT stickers_fk
366 REFERENCES sticker_packs(id)
369 CREATE TABLE sticker_references(
372 CONSTRAINT sticker_references_fk
374 REFERENCES sticker_packs(id)
378 shortName TEXT PRIMARY KEY,
381 CREATE TABLE messages(
382 rowid INTEGER PRIMARY KEY ASC,
388 schemaVersion INTEGER,
389 conversationId STRING,
392 hasAttachments INTEGER,
393 hasFileAttachments INTEGER,
394 hasVisualMediaAttachments INTEGER,
396 expirationStartTimestamp INTEGER,
399 messageTimer INTEGER,
400 messageTimerStart INTEGER,
401 messageTimerExpiresAt INTEGER,
404 sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
405 GENERATED ALWAYS AS (type IS
'story
'), isChangeCreatedByUs INTEGER NOT NULL DEFAULT
0, isTimerChangeFromSync INTEGER
406 GENERATED ALWAYS AS (
407 json_extract(json,
'$.expirationTimerUpdate.fromSync
') IS
1
408 ), seenStatus NUMBER default
0, storyDistributionListId STRING, expiresAt INT
411 expirationStartTimestamp + (expireTimer *
1000),
413 )), shouldAffectActivity INTEGER
414 GENERATED ALWAYS AS (
418 'change-number-notification
',
419 'contact-removed-notification
',
420 'conversation-merge
',
421 'group-v1-migration
',
423 'message-history-unsynced
',
424 'profile-change
',
426 'universal-timer-notification
',
427 'verified-change
'
429 ), shouldAffectPreview INTEGER
430 GENERATED ALWAYS AS (
434 'change-number-notification
',
435 'contact-removed-notification
',
436 'conversation-merge
',
437 'group-v1-migration
',
439 'message-history-unsynced
',
440 'profile-change
',
442 'universal-timer-notification
',
443 'verified-change
'
445 ), isUserInitiatedMessage INTEGER
446 GENERATED ALWAYS AS (
450 'change-number-notification
',
451 'contact-removed-notification
',
452 'conversation-merge
',
453 'group-v1-migration
',
454 'group-v2-change
',
456 'message-history-unsynced
',
457 'profile-change
',
459 'universal-timer-notification
',
460 'verified-change
'
462 ), mentionsMe INTEGER NOT NULL DEFAULT
0, isGroupLeaveEvent INTEGER
463 GENERATED ALWAYS AS (
464 type IS
'group-v2-change
' AND
465 json_array_length(json_extract(json,
'$.groupV2Change.details
')) IS
1 AND
466 json_extract(json,
'$.groupV2Change.details[
0].type
') IS
'member-remove
' AND
467 json_extract(json,
'$.groupV2Change.from
') IS NOT NULL AND
468 json_extract(json,
'$.groupV2Change.from
') IS json_extract(json,
'$.groupV2Change.details[
0].aci
')
469 ), isGroupLeaveEventFromOther INTEGER
470 GENERATED ALWAYS AS (
471 isGroupLeaveEvent IS
1
473 isChangeCreatedByUs IS
0
475 GENERATED ALWAYS AS (
476 json_extract(json,
'$.callId
')
478 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
481 queueType TEXT STRING NOT NULL,
482 timestamp INTEGER NOT NULL,
485 CREATE TABLE reactions(
486 conversationId STRING,
489 messageReceivedAt INTEGER,
490 targetAuthorAci STRING,
491 targetTimestamp INTEGER,
494 CREATE TABLE senderKeys(
495 id TEXT PRIMARY KEY NOT NULL,
496 senderId TEXT NOT NULL,
497 distributionId TEXT NOT NULL,
499 lastUpdatedDate NUMBER NOT NULL
501 CREATE TABLE unprocessed(
502 id STRING PRIMARY KEY ASC,
509 serverTimestamp INTEGER,
510 sourceServiceId STRING
511 , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
512 CREATE TABLE sendLogPayloads(
513 id INTEGER PRIMARY KEY ASC,
515 timestamp INTEGER NOT NULL,
516 contentHint INTEGER NOT NULL,
518 , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT
0 NOT NULL);
519 CREATE TABLE sendLogRecipients(
520 payloadId INTEGER NOT NULL,
522 recipientServiceId STRING NOT NULL,
523 deviceId INTEGER NOT NULL,
525 PRIMARY KEY (payloadId, recipientServiceId, deviceId),
527 CONSTRAINT sendLogRecipientsForeignKey
528 FOREIGN KEY (payloadId)
529 REFERENCES sendLogPayloads(id)
532 CREATE TABLE sendLogMessageIds(
533 payloadId INTEGER NOT NULL,
535 messageId STRING NOT NULL,
537 PRIMARY KEY (payloadId, messageId),
539 CONSTRAINT sendLogMessageIdsForeignKey
540 FOREIGN KEY (payloadId)
541 REFERENCES sendLogPayloads(id)
544 CREATE TABLE preKeys(
545 id STRING PRIMARY KEY ASC,
547 , ourServiceId NUMBER
548 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
549 CREATE TABLE signedPreKeys(
550 id STRING PRIMARY KEY ASC,
552 , ourServiceId NUMBER
553 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
556 category TEXT NOT NULL,
558 descriptionTemplate TEXT NOT NULL
560 CREATE TABLE badgeImageFiles(
561 badgeId TEXT REFERENCES badges(id)
564 'order
' INTEGER NOT NULL,
569 CREATE TABLE storyReads (
570 authorId STRING NOT NULL,
571 conversationId STRING NOT NULL,
572 storyId STRING NOT NULL,
573 storyReadDate NUMBER NOT NULL,
575 PRIMARY KEY (authorId, storyId)
577 CREATE TABLE storyDistributions(
578 id STRING PRIMARY KEY NOT NULL,
581 senderKeyInfoJson STRING
582 , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
583 CREATE TABLE storyDistributionMembers(
584 listId STRING NOT NULL REFERENCES storyDistributions(id)
587 serviceId STRING NOT NULL,
589 PRIMARY KEY (listId, serviceId)
591 CREATE TABLE uninstalled_sticker_packs (
592 id STRING NOT NULL PRIMARY KEY,
593 uninstalledAt NUMBER NOT NULL,
595 storageVersion NUMBER,
596 storageUnknownFields BLOB,
597 storageNeedsSync INTEGER NOT NULL
599 CREATE TABLE groupCallRingCancellations(
600 ringId INTEGER PRIMARY KEY,
601 createdAt INTEGER NOT NULL
603 CREATE TABLE IF NOT EXISTS
'messages_fts_data
'(id INTEGER PRIMARY KEY, block BLOB);
604 CREATE TABLE IF NOT EXISTS
'messages_fts_idx
'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
605 CREATE TABLE IF NOT EXISTS
'messages_fts_content
'(id INTEGER PRIMARY KEY, c0);
606 CREATE TABLE IF NOT EXISTS
'messages_fts_docsize
'(id INTEGER PRIMARY KEY, sz BLOB);
607 CREATE TABLE IF NOT EXISTS
'messages_fts_config
'(k PRIMARY KEY, v) WITHOUT ROWID;
608 CREATE TABLE edited_messages(
609 messageId STRING REFERENCES messages(id)
613 , conversationId STRING);
614 CREATE TABLE mentions (
615 messageId REFERENCES messages(id) ON DELETE CASCADE,
620 CREATE TABLE kyberPreKeys(
621 id STRING PRIMARY KEY NOT NULL,
622 json TEXT NOT NULL, ourServiceId NUMBER
623 GENERATED ALWAYS AS (json_extract(json,
'$.ourServiceId
')));
624 CREATE TABLE callsHistory (
625 callId TEXT PRIMARY KEY,
626 peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
627 ringerId TEXT DEFAULT NULL, -- ringer uuid
628 mode TEXT NOT NULL, -- enum
"Direct
" |
"Group
"
629 type TEXT NOT NULL, -- enum
"Audio
" |
"Video
" |
"Group
"
630 direction TEXT NOT NULL, -- enum
"Incoming
" |
"Outgoing
631 -- Direct: enum
"Pending
" |
"Missed
" |
"Accepted
" |
"Deleted
"
632 -- Group: enum
"GenericGroupCall
" |
"OutgoingRing
" |
"Ringing
" |
"Joined
" |
"Missed
" |
"Declined
" |
"Accepted
" |
"Deleted
"
633 status TEXT NOT NULL,
634 timestamp INTEGER NOT NULL,
635 UNIQUE (callId, peerId) ON CONFLICT FAIL
637 [ dropped all indexes to save space in this blog post ]
638 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
640 new.body IS NOT NULL AND new.isViewOnce =
1
642 DELETE FROM messages_fts WHERE rowid = old.rowid;
644 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
645 WHEN new.isViewOnce IS NOT
1 AND new.storyId IS NULL
647 INSERT INTO messages_fts
650 (new.rowid, new.body);
652 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
653 DELETE FROM messages_fts WHERE rowid = old.rowid;
654 DELETE FROM sendLogPayloads WHERE id IN (
655 SELECT payloadId FROM sendLogMessageIds
656 WHERE messageId = old.id
658 DELETE FROM reactions WHERE rowid IN (
659 SELECT rowid FROM reactions
660 WHERE messageId = old.id
662 DELETE FROM storyReads WHERE storyId = old.storyId;
664 CREATE VIRTUAL TABLE messages_fts USING fts5(
666 tokenize =
'signal_tokenizer
'
668 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
670 (new.body IS NULL OR old.body IS NOT new.body) AND
671 new.isViewOnce IS NOT
1 AND new.storyId IS NULL
673 DELETE FROM messages_fts WHERE rowid = old.rowid;
674 INSERT INTO messages_fts
677 (new.rowid, new.body);
679 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
681 INSERT INTO mentions (messageId, mentionAci, start, length)
683 SELECT messages.id, bodyRanges.value -
>> 'mentionAci
' as mentionAci,
684 bodyRanges.value -
>> 'start
' as start,
685 bodyRanges.value -
>> 'length
' as length
686 FROM messages, json_each(messages.json -
>> 'bodyRanges
') as bodyRanges
687 WHERE bodyRanges.value -
>> 'mentionAci
' IS NOT NULL
689 AND messages.id = new.id;
691 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
693 DELETE FROM mentions WHERE messageId = new.id;
694 INSERT INTO mentions (messageId, mentionAci, start, length)
696 SELECT messages.id, bodyRanges.value -
>> 'mentionAci
' as mentionAci,
697 bodyRanges.value -
>> 'start
' as start,
698 bodyRanges.value -
>> 'length
' as length
699 FROM messages, json_each(messages.json -
>> 'bodyRanges
') as bodyRanges
700 WHERE bodyRanges.value -
>> 'mentionAci
' IS NOT NULL
702 AND messages.id = new.id;
707 <p
>Finally I have the tool needed to inspect and process Signal
708 messages that I need, without using the vendor provided client. Now
709 on to transforming it to a more useful format.
</p
>
711 <p
>As usual, if you use Bitcoin and want to show your support of my
712 activities, please send Bitcoin donations to my address
713 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
718 <title>New chrpath release
0.17</title>
719 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html
</link>
720 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html
</guid>
721 <pubDate>Fri,
10 Nov
2023 07:
30:
00 +
0100</pubDate>
722 <description><p
>The chrpath package provide a simple command line tool to remove or
723 modify the rpath or runpath of compiled ELF program. It is almost
10
724 years since I updated the code base, but I stumbled over the tool
725 today, and decided it was time to move the code base from Subversion
726 to git and find a new home for it, as the previous one (Debian Alioth)
727 has been shut down. I decided to go with
728 <a href=
"https://codeberg.org/
">Codeberg
</a
> this time, as it is my git
729 service of choice these days, did a quick and dirty migration to git
730 and updated the code with a few patches I found in the Debian bug
731 tracker. These are the release notes:
</p
>
733 <p
>New in
0.17 released
2023-
11-
10:
</p
>
736 <li
>Moved project to Codeberg, as Alioth is shut down.
</li
>
737 <li
>Add Solaris support (use
&lt;sys/byteorder.h
> instead of
&lt;byteswap.h
>).
738 Patch from Rainer Orth.
</li
>
739 <li
>Added missing newline from printf() line. Patch from Frank Dana.
</li
>
740 <li
>Corrected handling of multiple ELF sections. Patch from Frank Dana.
</li
>
741 <li
>Updated build rules for .deb. Partly based on patch from djcj.
</li
>
744 <p
>The latest edition is tagged and available from
745 <a href=
"https://codeberg.org/pere/chrpath
">https://codeberg.org/pere/chrpath
</a
>.
747 <p
>As usual, if you use Bitcoin and want to show your support of my
748 activities, please send Bitcoin donations to my address
749 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
754 <title>Test framework for DocBook processors / formatters
</title>
755 <link>https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</link>
756 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</guid>
757 <pubDate>Sun,
5 Nov
2023 13:
00:
00 +
0100</pubDate>
758 <description><p
>All the books I have published so far has been using
759 <a href=
"https://docbook.org/
">DocBook
</a
> somewhere in the process.
760 For the first book, the source format was DocBook, while for every
761 later book it was an intermediate format used as the stepping stone to
762 be able to present the same manuscript in several formats, on paper,
763 as ebook in ePub format, as a HTML page and as a PDF file either for
764 paper production or for Internet consumption. This is made possible
765 with a wide variety of free software tools with DocBook support in
766 Debian. The source format of later books have been docx via rst,
767 Markdown, Filemaker and Asciidoc, and for all of these I was able to
768 generate a suitable DocBook file for further processing using
769 <a href=
"https://tracker.debian.org/pkg/pandoc
">pandoc
</a
>,
770 <a href=
"https://tracker.debian.org/pkg/asciidoc
">a2x
</a
> and
771 <a href=
"https://tracker.debian.org/pkg/asciidoctor
">asciidoctor
</a
>,
772 as well as rendering using
773 <a href=
"https://tracker.debian.org/pkg/xmlto
">xmlto
</a
>,
774 <a href=
"https://tracker.debian.org/pkg/dbtoepub
">dbtoepub
</a
>,
775 <a href=
"https://tracker.debian.org/pkg/dblatex
">dblatex
</a
>,
776 <a href=
"https://tracker.debian.org/pkg/docbook-xsl
">docbook-xsl
</a
> and
777 <a href=
"https://tracker.debian.org/pkg/fop
">fop
</a
>.
</p
>
779 <p
>Most of the
<a href=
"http://www.hungry.com/~pere/publisher/
">books I
780 have published
</a
> are translated books, with English as the source
782 <a href=
"https://tracker.debian.org/pkg/po4a
">po4a
</a
> to
783 handle translations using the gettext PO format has been a blessing,
784 but publishing translated books had triggered the need to ensure the
785 DocBook tools handle relevant languages correctly. For every new
786 language I have published, I had to submit patches dblatex, dbtoepub
787 and docbook-xsl fixing incorrect language and country specific issues
788 in the framework themselves. Typically this has been missing keywords
789 like
'figure
' or sort ordering of index entries. After a while it
790 became tiresome to only discover issues like this by accident, and I
791 decided to write a DocBook
"test framework
" exercising various
792 features of DocBook and allowing me to see all features exercised for
793 a given language. It consist of a set of DocBook files, a version
4
794 book, a version
5 book, a v4 book set, a v4 selection of problematic
795 tables, one v4 testing sidefloat and finally one v4 testing a book of
796 articles. The DocBook files are accompanied with a set of build rules
797 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
798 or docbook-xsl and epub using dbtoepub. The result is a set of files
799 visualizing footnotes, indexes, table of content list, figures,
800 formulas and other DocBook features, allowing for a quick review on
801 the completeness of the given locale settings. To build with a
802 different language setting, all one need to do is edit the lang= value
803 in the .xml file to pick a different ISO
639 code value and run
804 'make
'.
</p
>
806 <p
>The
<a href=
"https://codeberg.org/pere/docbook-example/
">test framework
807 source code
</a
> is available from Codeberg, and a generated set of
808 presentations of the various examples is available as Codeberg static
810 <a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
>.
811 Using this test framework I have been able to discover and report
812 several bugs and missing features in various tools, and got a lot of
813 them fixed. For example I got Northern Sami keywords added to both
814 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
815 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
816 Norwegian index sorting support fixed in xindy and initial Norwegian
817 Bokmål support added to dblatex. Some issues still remains, though.
818 Default index sorting rules are still broken in several tools, so the
819 Norwegian letters æ, ø and å are more often than not sorted properly
820 in the book index.
</p
>
822 <p
>The test framework recently received some more polish, as part of
823 publishing my latest book. This book contained a lot of fairly
824 complex tables, which exposed bugs in some of the tools. This made me
825 add a new test file with various tables, as well as spend some time to
826 brush up the build rules. My goal is for the test framework to
827 exercise all DocBook features to make it easier to see which features
828 work with different processors, and hopefully get them all to support
829 the full set of DocBook features. Feel free to send patches to extend
830 the test set, and test it with your favorite DocBook processor.
831 Please visit these two URLs to learn more:
</p
>
834 <li
><a href=
"https://codeberg.org/pere/docbook-example/
">https://codeberg.org/pere/docbook-example/
</a
></li
>
835 <li
><a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
></li
>
838 <p
>If you want to learn more on Docbook and translations, I recommend
839 having a look at the
<a href=
"https://docbook.org/
">the DocBook
841 <a href=
"https://doccookbook.sourceforge.net/html/en/
">the DoCookBook
842 site
<a/
> and my earlier blog post on
843 <a href=
"https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
">how
844 the Skolelinux project process and translate documentation
</a
>, a talk I gave earlier this year on
845 <a href=
"https://www.nuug.no/aktiviteter/
20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/
">how
846 to translate and publish books using free software
</a
> (Norwegian
851 https://github.com/docbook/xslt10-stylesheets/issues/
205 (docbook-xsl: sme support)
852 https://bugs.debian.org/
968437 (xindy: index sorting rules for nb/nn)
853 https://bugs.debian.org/
856123 (pandoc: markdown to docbook with non-english titles)
854 https://bugs.debian.org/
864813 (dblatex: missing nb words)
855 https://bugs.debian.org/
756386 (dblatex: index sorting rules for nb/nn)
856 https://bugs.debian.org/
796871 (dbtoepub: index sorting rules for nb/nn)
857 https://bugs.debian.org/
792616 (dblatex: PDF metadata)
858 https://bugs.debian.org/
686908 (docbook-xsl: index sorting rules for nb/nn)
859 https://sourceforge.net/tracker/?func=detail
&atid=
373747&aid=
3556630&group_id=
21935 (docbook-xsl: nb/nn support)
860 https://bugs.debian.org/
684391 (dblatex: initial nb support)
864 <p
>As usual, if you use Bitcoin and want to show your support of my
865 activities, please send Bitcoin donations to my address
866 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
871 <title>What did I learn from OpenSnitch this summer?
</title>
872 <link>https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</link>
873 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</guid>
874 <pubDate>Sun,
11 Jun
2023 08:
30:
00 +
0200</pubDate>
875 <description><p
>With yesterdays
876 <a href=
"https://www.debian.org/News/
2023/
20230610">release of Debian
877 12 Bookworm
</a
>, I am happy to know the
878 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
879 application firewall OpenSnitch
</a
> is available for a wider audience.
880 I have been running it for a few weeks now, and have been surprised
881 about some of the programs connecting to the Internet. Some programs
882 are obviously calling out from my machine, like the NTP network based
883 clock adjusting system and Tor to reach other Tor clients, but others
884 were more dubious. For example, the KDE Window manager try to look up
885 the host name in DNS, for no apparent reason, but if this lookup is
886 blocked the KDE desktop get periodically stuck when I use it. Another
887 surprise was how much Firefox call home directly to mozilla.com,
888 mozilla.net and googleapis.com, to mention a few, when I visit other
889 web pages. This direct connection happen even if I told Firefox to
890 always use a proxy, and the proxy setting is ignored for this traffic.
891 Other surprising connections come from audacity and dirmngr (I do not
892 use Gnome). It took some trial and error to get a good default set of
893 permissions. Without it, I would get popups asking for permissions at
894 any time, also the most inconvenient ones where I am in the middle of
895 a time sensitive gaming session.
</p
>
897 <p
>I suspect some application developers should rethink when then need
898 to use network connections or DNS lookups, and recommend testing
899 OpenSnitch (only
<tt
>apt install opensnitch
</tt
> away in Debian
900 Bookworm) to locate and report any surprising Internet connections on
901 your desktop machine.
</p
>
903 <p
>At the moment the upstream developer and Debian package maintainer
904 is working on making the system more reliable in Debian, by enabling
905 the eBPF kernel module to track processes and connections instead of
906 depending in content in /proc/. This should enter unstable fairly
909 <p
>As usual, if you use Bitcoin and want to show your support of my
910 activities, please send Bitcoin donations to my address
911 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
913 <p
><strong
>Update
2023-
06-
12</strong
>: I got a tip about
914 <a href=
"https://wiki.debian.org/PrivacyIssues
">a list of privacy
915 issues in Free Software
</a
> and the
916 <a href=
"irc://irc.debian.org/%
23debian-privacy
">#debian-privacy IRC
917 channel
</a
> discussing these topics.
</p
>
923 <title>wmbusmeters, parse data from your utility meter - nice free software
</title>
924 <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</link>
925 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</guid>
926 <pubDate>Fri,
19 May
2023 21:
50:
00 +
0200</pubDate>
927 <description><p
>There is a European standard for reading utility meters like water,
928 gas, electricity or heat distribution meters. The
929 <a href=
"https://en.wikipedia.org/wiki/Meter-Bus
">Meter-Bus standard
930 (EN
13757-
2, EN
13757-
3 and EN
13757–
4)
</a
> provide a cross vendor way
931 to talk to and collect meter data. I ran into this standard when I
932 wanted to monitor some heat distribution meters, and managed to find
933 free software that could do the job. The meters in question broadcast
934 encrypted messages with meter information via radio, and the hardest
935 part was to track down the encryption keys from the vendor. With this
936 in place I could set up a MQTT gateway to submit the meter data for
939 <p
>The free software systems in question,
940 <a href=
"https://tracker.debian.org/pkg/rtl-wmbus
">rtl-wmbus
</a
> to
941 read the messages from a software defined radio, and
942 <a href=
"https://tracker.debian.org/pkg/wmbusmeters
">wmbusmeters
</a
> to
943 decrypt and decode the content of the messages, is working very well
944 and allowe me to get frequent updates from my meters. I got in touch
945 with upstream last year to see if there was any interest in publishing
946 the packages via Debian. I was very happy to learn that Fredrik
947 Öhrström volunteered to maintain the packages, and I have since
948 assisted him in getting Debian package build rules in place as well as
949 sponsoring the packages into the Debian archive. Sadly we completed
950 it too late for them to become part of the next stable Debian release
951 (Bookworm). The wmbusmeters package just cleared the NEW queue. It
952 will need some work to fix a built problem, but I expect Fredrik will
953 find a solution soon.
</p
>
955 <p
>If you got a infrastructure meter supporting the Meter Bus
956 standard, I strongly recommend having a look at these nice
959 <p
>As usual, if you use Bitcoin and want to show your support of my
960 activities, please send Bitcoin donations to my address
961 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
966 <title>The
2023 LinuxCNC Norwegian developer gathering
</title>
967 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</link>
968 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</guid>
969 <pubDate>Sun,
14 May
2023 20:
30:
00 +
0200</pubDate>
970 <description><p
>The LinuxCNC project is making headway these days. A lot of
971 patches and issues have seen activity on
972 <a href=
"https://github.com/LinuxCNC/linuxcnc/
">the project github
973 pages
</a
> recently. A few weeks ago there was a developer gathering
974 over at the
<a href=
"https://tormach.com/
">Tormach
</a
> headquarter in
975 Wisconsin, and now we are planning a new gathering in Norway. If you
976 wonder what LinuxCNC is, lets quote Wikipedia:
</p
>
979 "LinuxCNC is a software system for numerical control of
980 machines such as milling machines, lathes, plasma cutters, routers,
981 cutting machines, robots and hexapods. It can control up to
9 axes or
982 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
983 several GUIs suited to specific kinds of usage (touch screen,
984 interactive development).
"
987 <p
>The Norwegian developer gathering take place the weekend June
16th
988 to
18th this year, and is open for everyone interested in contributing
989 to LinuxCNC. Up to date information about the gathering can be found
991 <a href=
"https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%
40hjemme.reinholdtsen.name/#msg37837251
">the
992 developer mailing list thread
</a
> where the gathering was announced.
993 Thanks to the good people at
994 <a href=
"https://www.debian.org/
">Debian
</a
>,
995 <a href=
"https://www.redpill-linpro.com/
">Redpill-Linpro
</a
> and
996 <a href=
"https://www.nuugfoundation.no/no/
">NUUG Foundation
</a
>, we
997 have enough sponsor funds to pay for food, and shelter for the people
998 traveling from afar to join us. If you would like to join the
999 gathering, get in touch.
</p
>
1001 <p
>As usual, if you use Bitcoin and want to show your support of my
1002 activities, please send Bitcoin donations to my address
1003 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1008 <title>OpenSnitch in Debian ready for prime time
</title>
1009 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</link>
1010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</guid>
1011 <pubDate>Sat,
13 May
2023 12:
10:
00 +
0200</pubDate>
1012 <description><p
>A bit delayed,
1013 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
1014 application firewall OpenSnitch
</a
> package in Debian now got the
1015 latest fixes ready for Debian Bookworm. Because it depend on a
1016 package missing on some architectures, the autopkgtest check of the
1017 testing migration script did not understand that the tests were
1018 actually working, so the migration was delayed. A bug in the package
1019 dependencies is also fixed, so those installing the firewall package
1020 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
1021 installed by default. I am very grateful to Gustavo Iñiguez Goya for
1022 his work on getting the package ready for Debian Bookworm.
</p
>
1024 <p
>Armed with this package I have discovered some surprising
1025 connections from programs I believed were able to work completly
1026 offline, and it has already proven its worth, at least to me. If you
1027 too want to get more familiar with the kind of programs using
1028 Internett connections on your machine, I recommend testing
<tt
>apt
1029 install opensnitch
</tt
> in Bookworm and see what you think.
</p
>
1031 <p
>The package is still not able to build its eBPF module within
1032 Debian. Not sure how much work it would be to get it working, but
1033 suspect some kernel related packages need to be extended with more
1034 header files to get it working.
</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>Speech to text, she APTly whispered, how hard can it be?
</title>
1044 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</link>
1045 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</guid>
1046 <pubDate>Sun,
23 Apr
2023 09:
40:
00 +
0200</pubDate>
1047 <description><p
>While visiting a convention during Easter, it occurred to me that
1048 it would be great if I could have a digital Dictaphone with
1049 transcribing capabilities, providing me with texts to cut-n-paste into
1050 stuff I need to write. The background is that long drives often bring
1051 up the urge to write on texts I am working on, which of course is out
1052 of the question while driving. With the release of
1053 <a href=
"https://github.com/openai/whisper/
">OpenAI Whisper
</a
>, this
1054 seem to be within reach with Free Software, so I decided to give it a
1055 go. OpenAI Whisper is a Linux based neural network system to read in
1056 audio files and provide text representation of the speech in that
1057 audio recording. It handle multiple languages and according to its
1058 creators even can translate into a different language than the spoken
1059 one. I have not tested the latter feature. It can either use the CPU
1060 or a GPU with CUDA support. As far as I can tell, CUDA in practice
1061 limit that feature to NVidia graphics cards. I have few of those, as
1062 they do not work great with free software drivers, and have not tested
1063 the GPU option. While looking into the matter, I did discover some
1064 work to provide CUDA support on non-NVidia GPUs, and some work with
1065 the library used by Whisper to port it to other GPUs, but have not
1066 spent much time looking into GPU support yet. I
've so far used an old
1067 X220 laptop as my test machine, and only transcribed using its
1070 <p
>As it from a privacy standpoint is unthinkable to use computers
1071 under control of someone else (aka a
"cloud
" service) to transcribe
1072 ones thoughts and personal notes, I want to run the transcribing
1073 system locally on my own computers. The only sensible approach to me
1074 is to make the effort I put into this available for any Linux user and
1075 to upload the needed packages into Debian. Looking at Debian Bookworm, I
1076 discovered that only three packages were missing,
1077 <a href=
"https://bugs.debian.org/
1034307">tiktoken
</a
>,
1078 <a href=
"https://bugs.debian.org/
1034144">triton
</a
>, and
1079 <a href=
"https://bugs.debian.org/
1034091">openai-whisper
</a
>. For a while
1081 <a href=
"https://bugs.debian.org/
1034286">ffmpeg-python
</a
> was
1083 <a href=
"https://github.com/kkroening/ffmpeg-python/issues/
760">upstream
1084 seem to have vanished
</a
> I found it safer
1085 <a href=
"https://github.com/openai/whisper/pull/
1242">to rewrite
1086 whisper
</a
> to stop depending on in than to introduce ffmpeg-python
1087 into Debian. I decided to place these packages under the umbrella of
1088 <a href=
"https://salsa.debian.org/deeplearning-team
">the Debian Deep
1089 Learning Team
</a
>, which seem like the best team to look after such
1090 packages. Discussing the topic within the group also made me aware
1091 that the triton package was already a future dependency of newer
1092 versions of the torch package being planned, and would be needed after
1093 Bookworm is released.
</p
>
1095 <p
>All required code packages have been now waiting in
1096 <a href=
"https://ftp-master.debian.org/new.html
">the Debian NEW
1097 queue
</a
> since Wednesday, heading for Debian Experimental until
1098 Bookworm is released. An unsolved issue is how to handle the neural
1099 network models used by Whisper. The default behaviour of Whisper is
1100 to require Internet connectivity and download the model requested to
1101 <tt
>~/.cache/whisper/
</tt
> on first invocation. This obviously would
1102 fail
<a href=
"https://people.debian.org/~bap/dfsg-faq.html
">the
1103 deserted island test of free software
</a
> as the Debian packages would
1104 be unusable for someone stranded with only the Debian archive and solar
1105 powered computer on a deserted island.
</p
>
1107 <p
>Because of this, I would love to include the models in the Debian
1108 mirror system. This is problematic, as the models are very large
1109 files, which would put a heavy strain on the Debian mirror
1110 infrastructure around the globe. The strain would be even higher if
1111 the models change often, which luckily as far as I can tell they do
1112 not. The small model, which according to its creator is most useful
1113 for English and in my experience is not doing a great job there
1114 either, is
462 MiB (deb is
414 MiB). The medium model, which to me
1115 seem to handle English speech fairly well is
1.5 GiB (deb is
1.3 GiB)
1116 and the large model is
2.9 GiB (deb is
2.6 GiB). I would assume
1117 everyone with enough resources would prefer to use the large model for
1118 highest quality. I believe the models themselves would have to go
1119 into the non-free part of the Debian archive, as they are not really
1120 including any useful source code for updating the models. The
1121 "source
", aka the model training set, according to the creators
1122 consist of
"680,
000 hours of multilingual and multitask supervised
1123 data collected from the web
", which to me reads material with both
1124 unknown copyright terms, unavailable to the general public. In other
1125 words, the source is not available according to the Debian Free
1126 Software Guidelines and the model should be considered non-free.
</p
>
1128 <p
>I asked the Debian FTP masters for advice regarding uploading a
1129 model package on their IRC channel, and based on the feedback there it
1130 is still unclear to me if such package would be accepted into the
1131 archive. In any case I wrote build rules for a
1132 <a href=
"https://salsa.debian.org/deeplearning-team/openai-whisper-model
">OpenAI
1133 Whisper model package
</a
> and
1134 <a href=
"https://github.com/openai/whisper/pull/
1257">modified the
1135 Whisper code base
</a
> to prefer shared files under
<tt
>/usr/
</tt
> and
1136 <tt
>/var/
</tt
> over user specific files in
<tt
>~/.cache/whisper/
</tt
>
1137 to be able to use these model packages, to prepare for such
1138 possibility. One solution might be to include only one of the models
1139 (small or medium, I guess) in the Debian archive, and ask people to
1140 download the others from the Internet. Not quite sure what to do
1141 here, and advice is most welcome (use the debian-ai mailing list).
</p
>
1143 <p
>To make it easier to test the new packages while I wait for them to
1144 clear the NEW queue, I created an APT source targeting bookworm. I
1145 selected Bookworm instead of Bullseye, even though I know the latter
1146 would reach more users, is that some of the required dependencies are
1147 missing from Bullseye and I during this phase of testing did not want
1148 to backport a lot of packages just to get up and running.
</p
>
1150 <p
>Here is a recipe to run as user root if you want to test OpenAI
1151 Whisper using Debian packages on your Debian Bookworm installation,
1152 first adding the APT repository GPG key to the list of trusted keys,
1153 then setting up the APT repository and finally installing the packages
1154 and one of the models:
</p
>
1156 <p
><pre
>
1157 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
1158 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
1159 mkdir -p /etc/apt/sources.list.d
1160 cat
> /etc/apt/sources.list.d/pere-whisper.list
&lt;
&lt;EOF
1161 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
1162 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
1165 apt install openai-whisper
1166 </pre
></p
>
1168 <p
>The package work for me, but have not yet been tested on any other
1169 computer than my own. With it, I have been able to (badly) transcribe
1170 a
2 minute
40 second Norwegian audio clip to test using the small
1171 model. This took
11 minutes and around
2.2 GiB of RAM. Transcribing
1172 the same file with the medium model gave a accurate text in
77 minutes
1173 using around
5.2 GiB of RAM. My test machine had too little memory to
1174 test the large model, which I believe require
11 GiB of RAM. In
1175 short, this now work for me using Debian packages, and I hope it will
1176 for you and everyone else once the packages enter Debian.
</p
>
1178 <p
>Now I can start on the audio recording part of this project.
</p
>
1180 <p
>As usual, if you use Bitcoin and want to show your support of my
1181 activities, please send Bitcoin donations to my address
1182 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1187 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software
</title>
1188 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</link>
1189 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</guid>
1190 <pubDate>Fri,
7 Apr
2023 23:
10:
00 +
0200</pubDate>
1191 <description><p
>Today I finally found time to track down a useful radio frequency
1192 scanner for my software defined radio. Just for fun I tried to locate
1193 the radios used in the areas, and a good start would be to scan all
1194 the frequencies to see what is in use. I
've tried to find a useful
1195 program earlier, but ran out of time before I managed to find a useful
1196 tool. This time I was more successful, and after a few false leads I
1197 found a description of
1198 <a href=
"https://www.kali.org/tools/rtlsdr-scanner/
">rtlsdr-scanner
1199 over at the Kali site
</a
>, and was able to track down
1200 <a href=
"https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git
">the
1201 Kali package git repository
</a
> to build a deb package for the
1202 scanner. Sadly the package is missing from the Debian project itself,
1203 at least in Debian Bullseye. Two runtime dependencies,
1204 <a href=
"https://gitlab.com/kalilinux/packages/python-visvis.git
">python-visvis
</a
>
1206 <a href=
"https://gitlab.com/kalilinux/packages/python-rtlsdr.git
">python-rtlsdr
</a
>
1207 had to be built and installed separately. Luckily
'<tt
>gbp
1208 buildpackage
</tt
>' handled them just fine and no further packages had
1209 to be manually built. The end result worked out of the box after
1210 installation.
</p
>
1212 <p
>My initial scans for FM channels worked just fine, so I knew the
1213 scanner was functioning. But when I tried to scan every frequency
1214 from
100 to
1000 MHz, the program stopped unexpectedly near the
1215 completion. After some debugging I discovered USB software radio I
1216 used rejected frequencies above
948 MHz, triggering a unreported
1217 exception breaking the scan. Changing the scan to end at
957 worked
1218 better. I similarly found the lower limit to be around
15, and ended
1219 up with the following full scan:
</p
>
1221 <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
>
1223 <p
>Saving the scan did not work, but exporting it as a CSV file worked
1224 just fine. I ended up with around
477k CVS lines with dB level for
1225 the given frequency.
</p
>
1227 <p
>The save failure seem to be a missing UTF-
8 encoding issue in the
1228 python code. Will see if I can find time to send a patch
1229 <a href=
"https://github.com/CdeMills/RTLSDR-Scanner/
">upstream
</a
>
1230 later to fix this exception:
</p
>
1233 Traceback (most recent call last):
1234 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
1235 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
1236 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
1237 handle.write(json.dumps(data, indent=
4))
1238 TypeError: a bytes-like object is required, not
'str
'
1239 Traceback (most recent call last):
1240 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
1241 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
1242 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
1243 handle.write(json.dumps(data, indent=
4))
1244 TypeError: a bytes-like object is required, not
'str
'
1247 <p
>As usual, if you use Bitcoin and want to show your support of my
1248 activities, please send Bitcoin donations to my address
1249 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1254 <title>OpenSnitch available in Debian Sid and Bookworm
</title>
1255 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</link>
1256 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</guid>
1257 <pubDate>Sat,
25 Feb
2023 20:
30:
00 +
0100</pubDate>
1258 <description><p
>Thanks to the efforts of the OpenSnitch lead developer Gustavo
1259 Iñiguez Goya allowing me to sponsor the upload,
1260 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
1261 application firewall OpenSnitch
</a
> is now available in Debian
1262 Testing, soon to become the next stable release of Debian.
</p
>
1264 <p
>This is a package which set up a network firewall on one or more
1265 machines, which is controlled by a graphical user interface that will
1266 ask the user if a program should be allowed to connect to the local
1267 network or the Internet. If some background daemon is trying to dial
1268 home, it can be blocked from doing so with a simple mouse click, or by
1269 default simply by not doing anything when the GUI question dialog pop
1270 up. A list of all programs discovered using the network is provided
1271 in the GUI, giving the user an overview of how the machine(s) programs
1272 use the network.
</p
>
1274 <p
>OpenSnitch was uploaded for NEW processing about a month ago, and I
1275 had little hope of it getting accepted and shaping up in time for the
1276 package freeze, but the Debian ftpmasters proved to be amazingly quick
1277 at checking out the package and it was accepted into the archive about
1278 week after the first upload. It is now team maintained under the Go
1279 language team umbrella. A few fixes to the default setup is only in
1280 Sid, and should migrate to Testing/Bookworm in a week.
</p
>
1282 <p
>During testing I ran into an
1283 <a href=
"https://github.com/evilsocket/opensnitch/issues/
813">issue
1284 with Minecraft server broadcasts disappearing
</a
>, which was quickly
1285 resolved by the developer with a patch and a proposed configuration
1286 change. I
've been told this was caused by the Debian packages default
1287 use if /proc/ information to track down kernel status, instead of the
1288 newer eBPF module that can be used. The reason is simply that
1289 upstream and I have failed to find a way to build the eBPF modules for
1290 OpenSnitch without a complete configured Linux kernel source tree,
1291 which as far as we can tell is unavailable as a build dependency in
1292 Debian. We tried unsuccessfully so far to use the kernel-headers
1293 package. It would be great if someone could provide some clues how to
1294 build eBPF modules on build daemons in Debian, possibly without the full
1295 kernel source.
</p
>
1297 <p
>As usual, if you use Bitcoin and want to show your support of my
1298 activities, please send Bitcoin donations to my address
1299 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1304 <title>Is the desktop recommending your program for opening its files?
</title>
1305 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
1306 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
1307 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
1308 <description><p
>Linux desktop systems
1309 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
1310 standardized
</a
> how programs present themselves to the desktop
1311 system. If a package include a .desktop file in
1312 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
1313 environments will pick up the file and use its content to generate the
1314 menu of available programs in the system. A lesser known fact is that
1315 a package can also explain to the desktop system how to recognize the
1316 files created by the program in question, and use it to open these
1317 files on request, for example via a GUI file browser.
</p
>
1319 <p
>A while back I ran into a package that did not tell the desktop
1320 system how to recognize its files and was not used to open its files
1321 in the file browser and fixed it. In the process I wrote a simple
1322 debian/tests/ script to ensure the setup keep working. It might be
1323 useful for other packages too, to ensure any future version of the
1324 package keep handling its own files.
</p
>
1326 <p
>For this to work the file format need a useful MIME type that can
1327 be used to identify the format. If the file format do not yet have a
1328 MIME type, it should define one and preferably also
1329 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
1330 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
1332 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
1333 query the database of standardized package information and ensure it
1334 return sensible values. It also need the location of an example file
1335 for xdg-mime to guess the format of.
</p
>
1340 # Author: Petter Reinholdtsen
1341 # License: GPL v2 or later at your choice.
1343 # Validate the MIME setup, making sure motor types have
1344 # application/vnd.openmotor+yaml associated with them and is connected
1345 # to the openmotor desktop file.
1349 mimetype=
"application/vnd.openmotor+yaml
"
1350 testfile=
"test/data/real/o3100/motor.ric
"
1351 mydesktopfile=
"openmotor.desktop
"
1353 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
1355 if [
"$mimetype
" !=
"$filemime
" ] ; then
1357 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
1359 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
1362 desktop=$(xdg-mime query default
"$mimetype
")
1364 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
1366 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
1368 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
1374 <p
>It is a simple way to ensure your users are not very surprised when
1375 they try to open one of your file formats in their file browser.
</p
>
1377 <p
>As usual, if you use Bitcoin and want to show your support of my
1378 activities, please send Bitcoin donations to my address
1379 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1384 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
1385 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
1386 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
1387 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
1388 <description><p
>While reading a
1389 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
1390 post claiming MacOS X recently started scanning local files and
1391 reporting information about them to Apple
</a
>, even on a machine where
1392 all such callback features had been disabled, I came across a
1393 description of the Little Snitch application for MacOS X. It seemed
1394 like a very nice tool to have in the tool box, and I decided to see if
1395 something similar was available for Linux.
</p
>
1397 <p
>It did not take long to find
1398 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
1399 package
</a
>, which has been in development since
2017, and now is in
1400 version
1.5.0. It has had a
1401 <a href=
"https://bugs.debian.org/
909567">request for Debian
1402 packaging
</a
> since
2018, but no-one completed the job so far. Just
1403 for fun, I decided to see if I could help, and I was very happy to
1405 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
1406 want a Debian package too
</a
>.
</p
>
1408 <p
>After struggling a bit with getting the program to run, figuring
1409 out building Go programs (and a little failed detour to look at eBPF
1410 builds too - help needed), I am very happy to report that I am
1411 sponsoring upstream to maintain the package in Debian, and it has
1412 since this morning been waiting in NEW for the ftpmasters to have a
1413 look. Perhaps it can get into the archive in time for the Bookworm
1416 <p
>As usual, if you use Bitcoin and want to show your support of my
1417 activities, please send Bitcoin donations to my address
1418 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1423 <title>LinuxCNC MQTT publisher component
</title>
1424 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
1425 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
1426 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
1427 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
1428 video from Andreas Schiffler
</a
> the other day, where he set up
1429 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
1430 information to the MQTT broker IBM Bluemix. As I also use MQTT for
1431 graphing, it occured to me that a generic MQTT LinuxCNC component
1432 would be useful and I set out to implement it. Today I got the first
1433 draft limping along and submitted as
1434 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
1435 LinuxCNC project
</a
>.
</p
>
1437 <p
>The simple part was setting up the MQTT publishing code in Python.
1438 I already have set up other parts submitting data to my Mosquito MQTT
1439 broker, so I could reuse that code. Writing a LinuxCNC component in
1440 Python as new to me, but using existing examples in the code
1441 repository and the extensive documentation, this was fairly straight
1442 forward. The hardest part was creating a automated test for the
1443 component to ensure it was working. Testing it in a simulated
1444 LinuxCNC machine proved very useful, as I discovered features I needed
1445 that I had not thought of yet, and adjusted the code quite a bit to
1446 make it easier to test without a operational MQTT broker
1447 available.
</p
>
1449 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
1450 pins I should collect and publish by default (in other words, the
1451 default set of information pieces published), and how to get the
1452 machine name from the LinuxCNC INI file. The latter is a minor
1453 detail, but I expect it would be useful in a setup with several
1454 machines available. I am hoping for feedback from the experienced
1455 LinuxCNC developers and users, to make the component even better
1456 before it can go into the mainland LinuxCNC code base.
</p
>
1458 <p
>Since I started on the MQTT component, I came across
1459 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
1460 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
1461 controlled by a Raspberry Pi, and it occured to me that it would
1462 be useful for such use cases if LinuxCNC also provided a REST API for
1463 querying its status. I hope to start on such component once the MQTT
1464 component is working well.
</p
>
1466 <p
>As usual, if you use Bitcoin and want to show your support of my
1467 activities, please send Bitcoin donations to my address
1468 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1473 <title>ONVIF IP camera management tool finally in Debian
</title>
1474 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
1475 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
1476 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
1477 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
1478 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
1479 specification
</a
>. There is finally a nice command line and GUI tool
1480 in Debian to manage ONVIF IP cameras. After working with upstream for
1481 a few months and sponsoring the upload, I am very happy to report that
1482 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
1483 entered Debian Sid last night.
</p
>
1485 <p
>The package provide a C library to communicate with such cameras, a
1486 command line tool to locate and update settings of (like password) the
1487 cameras and a GUI tool to configure and control the units as well as
1488 preview the video from the camera. Libonvif is available on Both
1489 Linux and Windows and the GUI tool uses the Qt library. The main
1490 competitors are non-free software, while libonvif is GNU GPL licensed.
1491 I am very glad Debian users in the future can control their cameras
1492 using a free software system provided by Debian. But the ONVIF world
1493 is full of slightly broken firmware, where the cameras pretend to
1494 follow the ONVIF specification but fail to set some configuration
1495 values or refuse to provide video to more than one recipient at the
1496 time, and the onvif project is quite young and might take a while
1497 before it completely work with your camera. Upstream seem eager to
1498 improve the library, so handling any broken camera might be just
<a
1499 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
1501 <p
>The package just cleared NEW, and need a new source only upload
1502 before it can enter testing. This will happen in the next few
1505 <p
>As usual, if you use Bitcoin and want to show your support of my
1506 activities, please send Bitcoin donations to my address
1507 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1512 <title>Managing and using ONVIF IP cameras with Linux
</title>
1513 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
1514 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
1515 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
1516 <description><p
>Recently I have been looking at how to control and collect data
1517 from a handful IP cameras using Linux. I both wanted to change their
1518 settings and to make their imagery available via a free software
1519 service under my control. Here is a summary of the tools I found.
</p
>
1521 <p
>First I had to identify the cameras and their protocols. As far as
1522 I could tell, they were using some SOAP looking protocol and their
1523 internal web server seem to only work with Microsoft Internet Explorer
1524 with some proprietary binary plugin, which in these days of course is
1525 a security disaster and also made it impossible for me to use the
1526 camera web interface. Luckily I discovered that the SOAP looking
1527 protocol is actually following
<a href=
"https://www.onvif.org/
">the
1528 ONVIF specification
</a
>, which seem to be supported by a lot of IP
1529 cameras these days.
</p
>
1531 <p
>Once the protocol was identified, I was able to find what appear to
1532 be the most popular way to configure ONVIF cameras, the free software
1534 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
1535 Manager
</a
>. Lacking any other options at the time, I tried
1536 unsuccessfully to get it running using Wine, but was missing a dotnet
1537 40 library and I found no way around it to run it on Linux.
</p
>
1539 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
1540 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
1541 Device Tool
</a
>. I did not like its terms of use, so did not spend
1542 much time on it.
</p
>
1544 <p
>To collect the video and make it available in a web interface, I
1545 found the Zoneminder tool in Debian. A recent version was able to
1546 automatically detect and configure ONVIF devices, so I could use it to
1547 set up motion detection in and collection of the camera output. I had
1548 initial problems getting the ONVIF autodetection to work, as both
1549 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
1550 the inter-tab communication
</a
> being used by the Zoneminder web
1551 pages, but managed to get konqueror to work. Apparently the
"Enhanced
1552 Tracking Protection
" in Firefox cause the problem. I ended up
1553 upgrading to the Bookworm edition of Zoneminder in the process to try
1554 to fix the issue, and believe the problem might be solved now.
</p
>
1556 <p
>In the process I came across the nice Linux GUI tool
1557 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
1558 allowing me to preview the camera output and validate the login
1559 passwords required. Sadly its author has grown tired of maintaining
1560 the software, so it might not see any future updates. Which is sad,
1561 as the viewer is sightly unstable and the picture tend to lock up.
1562 Note, this lockup might be due to limitations in the cameras and not
1563 the viewer implementation. I suspect the camera is only able to
1564 provide pictures to one client at the time, and the Zoneminder feed
1565 might interfere with the GUI viewer. I have
1566 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
1567 included in Debian
</a
>.
</p
>
1569 <p
>Finally, I found what appear to be very nice Linux free software
1570 replacement for the Windows tool, named
1571 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
1572 provide a C library to talk to ONVIF devices as well as a command line
1573 and GUI tool using the library. Using the GUI tool I was able to change
1574 the admin passwords and update other settings of the cameras. I have
1575 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
1576 included in Debian
</a
>.
</p
>
1578 <p
>As usual, if you use Bitcoin and want to show your support of my
1579 activities, please send Bitcoin donations to my address
1580 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1582 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
1583 this text, I got several suggestions for more free software Linux
1584 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
1585 ONVIF python library
</a
> (already
1586 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
1587 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
1588 fork
</a
> using a different SOAP dependency. There is also
1589 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
1590 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
1591 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
1592 two are not included in Debian either. I have not tested any of these
1598 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
1599 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
1600 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
1601 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
1602 <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
>
1604 <p
>(The picture is of the previous edition.)
</p
>
1606 <p
>Almost two years after the previous Norwegian Bokmål translation of
1607 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1608 Handbook
</a
>" was published, a new edition is finally being prepared. The
1609 english text is updated, and it is time to start working on the
1610 translations. Around
37 percent of the strings have been updated, one
1611 way or another, and the translations starting from a complete Debian Buster
1612 edition now need to bring their translation up from
63% to
100%. The
1613 complete book is licensed using a Creative Commons license, and has
1614 been published in several languages over the years. The translations
1615 are done by volunteers to bring Linux in their native tongue. The
1616 last time I checked, it complete text was available in English,
1617 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
1618 In addition, work has been started for Arabic (Morocco), Catalan,
1619 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
1620 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
1621 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
1623 <p
>The translation is conducted on
1624 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1625 hosted weblate project page
</a
>. Prospective translators are
1626 recommeded to subscribe to
1627 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1628 translators mailing list
</a
> and should also check out
1629 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1630 contributors
</a
>.
</p
>
1632 <p
>I am one of the Norwegian Bokmål translators of this book, and we
1633 have just started. Your contribution is most welcome.
</p
>
1635 <p
>As usual, if you use Bitcoin and want to show your support of my
1636 activities, please send Bitcoin donations to my address
1637 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1642 <title>Automatic LinuxCNC servo PID tuning?
</title>
1643 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
1644 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
1645 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
1646 <description><p
>While working on a CNC with servo motors controlled by the
1647 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
1648 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
1649 controller
</a
>, I recently had to learn how to tune the collection of values
1650 that control such mathematical machinery that a PID controller is. It
1651 proved to be a lot harder than I hoped, and I still have not succeeded
1652 in getting the Z PID controller to successfully defy gravity, nor X
1653 and Y to move accurately and reliably. But while climbing up this
1654 rather steep learning curve, I discovered that some motor control
1655 systems are able to tune their PID controllers. I got the impression
1656 from the documentation that LinuxCNC were not. This proved to be not
1659 <p
>The LinuxCNC
1660 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
1661 component
</a
> is the recommended PID controller to use. It uses eight
1662 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
1663 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
1664 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
1665 state, and all of these need to have a sensible value for the
1666 controller to behave properly. Note, there are even more values
1667 involved, theser are just the most important ones. In my case I need
1668 the X, Y and Z axes to follow the requested path with little error.
1669 This has proved quite a challenge for someone who have never tuned a
1670 PID controller before, but there is at least some help to be found.
1672 <p
>I discovered that included in LinuxCNC was this old PID component
1673 at_pid claiming to have auto tuning capabilities. Sadly it had been
1674 neglected since
2011, and could not be used as a plug in replacement
1675 for the default pid component. One would have to rewriting the
1676 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
1677 to quickly test auto tuning to see if it did a better job than me at
1678 figuring out good P, I and D values to use.
</p
>
1680 <p
>I decided to have a look if the situation could be improved. This
1681 involved trying to understand the code and history of the pid and
1682 at_pid components. Apparently they had a common ancestor, as code
1683 structure, comments and variable names were quite close to each other.
1684 Sadly this was not reflected in the git history, making it hard to
1685 figure out what really happened. My guess is that the author of
1686 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
1688 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
1689 rewrote it to follow the structure he wished pid.c to have, then added
1690 support for auto tuning and finally got it included into the LinuxCNC
1691 repository. The restructuring and lack of early history made it
1692 harder to figure out which part of the code were relevant to the auto
1693 tuning, and which part of the code needed to be updated to work the
1694 same way as the current pid.c implementation. I started by trying to
1695 isolate relevant changes in pid.c, and applying them to at_pid.c. My
1696 aim was to make sure the at_pid component could replace the pid
1697 component with a simple change in the HAL setup loadrt line, without
1698 having to
"rewire
" the rest of the HAL configuration. After a few
1699 hours following this approach, I had learned quite a lot about the
1700 code structure of both components, while concluding I was heading down
1701 the wrong rabbit hole, and should get back to the surface and find a
1702 different path.
</p
>
1704 <p
>For the second attempt, I decided to throw away all the PID control
1705 related part of the original at_pid.c, and instead isolate and lift
1706 the auto tuning part of the code and inject it into a copy of pid.c.
1707 This ensured compatibility with the current pid component, while
1708 adding auto tuning as a run time option. To make it easier to identify
1709 the relevant parts in the future, I wrapped all the auto tuning code
1710 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
1711 pid component by default, as that part of the code is identical. The
1712 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
1713 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
1715 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
1716 component. The most important ones are
<tt
>tune-effort
</tt
>,
1717 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
1718 back, and see what the auto tuning code will do. I do not know the
1719 mathematical foundation of the at_pid algorithm, but from observation
1720 I can tell that the algorithm will, when enabled, produce a square
1721 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
1722 of the PID controller. This can be seen using the HAL Scope provided
1723 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
1724 to the motor controller, which in turn is translated into motor speed.
1725 So at_pid will ask the motor to move the axis back and forth. The
1726 number of cycles in the pattern is controlled by the
1727 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
1728 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
1729 change the direction of a physical object instantly (as in going
1730 directly from a positive voltage to the equivalent negative voltage)
1731 do not change velocity instantly, and it take some time for the object
1732 to slow down and move in the opposite direction. This result in a
1733 more smooth movement wave form, as the axis in question were vibrating
1734 back and forth. When the axis reached the target speed in the
1735 opposing direction, the auto tuner change direction again. After
1736 several of these changes, the average time delay between the
'peaks
'
1737 and
'valleys
' of this movement graph is then used to calculate
1738 proposed values for Pgain, Igain and Dgain, and insert them into the
1739 HAL model to use by the pid controller. The auto tuned settings are
1740 not great, but htye work a lot better than the values I had been able
1741 to cook up on my own, at least for the horizontal X and Y axis. But I
1742 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
1743 controllers error out if the voltage change too quickly. I
've been
1744 less lucky with the Z axis, which is moving a heavy object up and
1745 down, and seem to confuse the algorithm. The Z axis movement became a
1746 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
1747 gravitational drag, but I will have to work a lot more on the Z axis
1748 PID values.
</p
>
1750 <p
>Armed with this knowledge, it is time to look at how to do the
1751 tuning. Lets say the HAL configuration in question load the PID
1752 component for X, Y and Z like this:
</p
>
1754 <blockquote
><pre
>
1755 loadrt pid names=pid.x,pid.y,pid.z
1756 </pre
></blockquote
>
1758 <p
>Armed with the new and improved at_pid component, the new line will
1759 look like this:
</p
>
1761 <blockquote
><pre
>
1762 loadrt at_pid names=pid.x,pid.y,pid.z
1763 </pre
></blockquote
>
1765 <p
>The rest of the HAL setup can stay the same. This work because the
1766 components are referenced by name. If the component had used count=
3
1767 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
1769 <p
>To start tuning the X axis, move the axis to the middle of its
1770 range, to make sure it do not hit anything when it start moving back
1771 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
1772 output range. I used
0.1 as my initial value. Next, assign
1 to the
1773 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
1774 part and feed
0 to the output pin, which in my case initially caused a
1775 lot of drift. In my case it proved to be a good idea with X and Y to
1776 tune the motor driver to make sure
0 voltage stopped the motor
1777 rotation. On the other hand, for the Z axis this proved to be a bad
1778 idea, so it will depend on your setup. It might help to set the
1779 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
1780 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
1781 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
1782 your axis will vibrate for a few seconds and when it is done, new
1783 values for Pgain, Igain and Dgain will be active. To test them,
1784 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
1785 machine to suddenly jerk as it bring the axis back to its commanded
1786 position, which it might have drifted away from during tuning. To
1787 summarize with some halcmd lines:
</p
>
1789 <blockquote
><pre
>
1790 setp pid.x.tune-effort
0.1
1791 setp pid.x.tune-mode
1
1792 setp pid.x.tune-start
1
1793 # wait for the tuning to complete
1794 setp pid.x.tune-mode
0
1795 </pre
></blockquote
>
1797 <p
>After doing this task quite a few times while trying to figure out
1798 how to properly tune the PID controllers on the machine in, I decided
1799 to figure out if this process could be automated, and wrote a script
1800 to do the entire tuning process from power on. The end result will
1801 ensure the machine is powered on and ready to run, home all axis if it
1802 is not already done, check that the extra tuning pins are available,
1803 move the axis to its mid point, run the auto tuning and re-enable the
1804 pid controller when it is done. It can be run several times. Check
1806 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
1807 script on github if you want to learn how it is done.
</p
>
1809 <p
>My hope is that this little adventure can inspire someone who know
1810 more about motor PID controller tuning can implement even better
1811 algorithms for automatic PID tuning in LinuxCNC, making life easier
1812 for both me and all the others that want to use LinuxCNC but lack the
1813 in depth knowledge needed to tune PID controllers well.
</p
>
1815 <p
>As usual, if you use Bitcoin and want to show your support of my
1816 activities, please send Bitcoin donations to my address
1817 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1822 <title>LinuxCNC translators life just got a bit easier
</title>
1823 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
1824 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
1825 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
1826 <description><p
>Back in oktober last year, when I started looking at the
1827 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
1828 proposed to change the documentation build system make life easier for
1829 translators. The original system consisted of independently written
1830 documentation files for each language, with no automated way to track
1831 changes done in other translations and no help for the translators to
1832 know how much was left to translated. By using
1833 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
1834 files from the English documentation, this can be improved. A small
1835 team of LinuxCNC contributors got together and today our labour
1836 finally payed off. Since a few hours ago, it is now possible to
1837 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
1838 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
1840 <p
>The effort to migrate the documentation to use po4a has been both
1841 slow and frustrating. I am very happy we finally made it.
</p
>
1843 <p
>As usual, if you use Bitcoin and want to show your support of my
1844 activities, please send Bitcoin donations to my address
1845 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1850 <title>geteltorito make CD firmware upgrades a breeze
</title>
1851 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
1852 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
1853 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
1854 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
1855 located the firmware download page from Lenovo (which annoyingly do
1856 not allow access via Tor, forcing me to hand them more personal
1857 information that I would like). The
1858 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
1859 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
1860 when all I got available is a USB memory stick. I tried booting the
1861 ISO as a USB stick, but this did not work. But genisoimage came to
1862 the rescue.
</p
>
1864 <P
>The geteltorito program in
1865 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
1866 package
</a
> is able to convert the bootable ISO image to a bootable
1867 USB stick using a simple command line recipe, which I then can write
1868 to the most recently inserted USB stick:
</p
>
1870 <blockquote
><pre
>
1871 geteltorito -o usbstick.img lenovo-firmware.iso
1872 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
1873 </pre
></blockquote
>
1875 <p
>This USB stick booted the firmware upgrader just fine, and in a few
1876 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
1881 <title>Run your industrial metal working machine using Debian?
</title>
1882 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
1883 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
1884 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
1885 <description><p
>After many months of hard work by the good people involved in
1886 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
1887 system was accepted Sunday
1888 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
1889 Once it was available from Debian, I was surprised to discover from
1890 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
1891 popularity-contest numbers
</a
> that people have been reporting its use
1892 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
1893 be a good place to check out, but sadly is not working when visiting
1896 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
1897 Wikipedia quote is in place?
</p
>
1900 "LinuxCNC is a software system for numerical control of
1901 machines such as milling machines, lathes, plasma cutters, routers,
1902 cutting machines, robots and hexapods. It can control up to
9 axes or
1903 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
1904 several GUIs suited to specific kinds of usage (touch screen,
1905 interactive development).
"
1908 <p
>It can even control
3D printers. And even though the Wikipedia
1909 page indicate that it can only work with hard real time kernel
1910 features, it can also work with the user space soft real time features
1911 provided by the Debian kernel.
1912 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
1913 available from Github. The last few months I
've been involved in the
1914 translation setup for the program and documentation. Translators are
1916 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
1917 effort
</a
> using Weblate.
</p
>
1919 <p
>As usual, if you use Bitcoin and want to show your support of my
1920 activities, please send Bitcoin donations to my address
1921 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1926 <title>Debian still an excellent choice for Lego builders
</title>
1927 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
1928 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
1929 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
1930 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
1931 the packages under the team umbrella has been updated to fix
1932 packaging, lintian issues and BTS reports. In addition, a new and
1933 inspiring team member appeared on both the
1934 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
1935 Team mailing list
</a
> and
1936 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
1937 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
1938 Mindstorms programming, check out the
1939 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
1940 see what Debian can offer the Lego enthusiast.
</p
>
1942 <p
>Patches has been sent upstream, causing new upstream releases, one
1943 even the first one in more than ten years, and old upstreams was
1944 released with new ones. There are still a lot of work left, and the
1945 team welcome more members to help us make sure Debian is the Linux
1946 distribution of choice for Lego builders. If you want to contribute,
1947 join us in the IRC channel and become part of
1948 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
1949 Salsa
</a
>.
</p
>
1951 <p
>As usual, if you use Bitcoin and want to show your support of my
1952 activities, please send Bitcoin donations to my address
1953 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1958 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
1959 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
1960 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
1961 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
1962 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
1963 Debian Administrator
's Handbook
</a
> is available in six languages now.
1964 I am not sure which one of these are completely proof read, but the
1965 complete book is available in these languages:
1969 <li
>English
</li
>
1970 <li
>Norwegian Bokmål
</li
>
1971 <li
>German
</li
>
1972 <li
>Indonesian
</li
>
1973 <li
>Brazil Portuguese
</li
>
1974 <li
>Spanish
</li
>
1978 <p
>This is the list of languages more than
70% complete, in other
1979 words with not too much left to do:
</p
>
1983 <li
>Chinese (Simplified) -
90%
</li
>
1984 <li
>French -
79%
</li
>
1985 <li
>Italian -
79%
</li
>
1986 <li
>Japanese -
77%
</li
>
1987 <li
>Arabic (Morocco) -
75%
</li
>
1988 <li
>Persian -
71%
</li
>
1992 <p
>I wonder how long it will take to bring these to
100%.
</p
>
1994 <p
>Then there is the list of languages about halfway done:
</p
>
1998 <li
>Russian -
63%
</li
>
1999 <li
>Swedish -
53%
</li
>
2000 <li
>Chinese (Traditional) -
46%
</li
>
2001 <li
>Catalan -
45%
</li
>
2005 <p
>Several are on to a good start:
</p
>
2009 <li
>Dutch -
26%
</li
>
2010 <li
>Vietnamese -
25%
</li
>
2011 <li
>Polish -
23%
</li
>
2012 <li
>Czech -
22%
</li
>
2013 <li
>Turkish -
18%
</li
>
2017 <p
>Finally, there are the ones just getting started:
</p
>
2021 <li
>Korean -
4%
</li
>
2022 <li
>Croatian -
2%
</li
>
2023 <li
>Greek -
2%
</li
>
2024 <li
>Danish -
1%
</li
>
2025 <li
>Romanian -
1%
</li
>
2029 <p
>If you want to help provide a Debian instruction book in your own
2031 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
2032 to contribute to the translations.
</p
>
2034 <p
>As usual, if you use Bitcoin and want to show your support of my
2035 activities, please send Bitcoin donations to my address
2036 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2041 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
2042 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
2043 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
2044 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
2045 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
2046 others, the decentralized communication platform
2047 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
2048 (earlier known as Ring), managed to get
2049 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
2050 into Debian Testing. Several of its dependencies has caused build and
2051 propagation problems, which all seem to be solved now.
</p
>
2053 <p
>In addition to the fact that Jami is decentralized, similar to how
2054 bittorrent is decentralized, I first of all like how it is not
2055 connected to external IDs like phone numbers. This allow me to set up
2056 computers to send me notifications using Jami without having to find
2057 get a phone number for each computer. Automatic notification via Jami
2058 is also made trivial thanks to the provided client side API (as a DBus
2059 service). Here is my bourne shell script demonstrating how to let any
2060 system send a message to any Jami address. It will create a new
2061 identity before sending the message, if no Jami identity exist
2064 <p
><pre
>
2067 # Usage: $
0 <jami-address
> <message
>
2069 # Send
<message
> to
<jami-address
>, create local jami account if
2072 # License: GPL v2 or later at your choice
2073 # Author: Petter Reinholdtsen
2076 if [ -z
"$HOME
" ] ; then
2077 echo
"error: missing \$HOME, required for dbus to work
"
2081 # First, get dbus running if not already running
2082 DBUSLAUNCH=/usr/bin/dbus-launch
2083 PIDFILE=/run/asterisk/dbus-session.pid
2084 if [ -e $PIDFILE ] ; then
2086 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
2087 unset DBUS_SESSION_BUS_ADDRESS
2090 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
2091 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
2092 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
2093 DBUS_SESSION_BUS_PID=$!
2095 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
2096 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
2097 echo export DBUS_SESSION_BUS_ADDRESS
2103 part=
"$
1"; shift
2104 op=
"$
1"; shift
2105 dbus-send --session \
2106 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
2110 part=
"$
1"; shift
2111 op=
"$
1"; shift
2112 dbus-send --session --print-reply \
2113 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
2117 dringopreply ConfigurationManager getAccountList | \
2118 grep string | awk -F
'"' '{print $
2}
' | head -n
1
2121 account=$(firstaccount)
2123 if [ -z
"$account
" ] ; then
2124 echo
"Missing local account, trying to create it
"
2125 dringop ConfigurationManager addAccount \
2126 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
2127 account=$(firstaccount)
2128 if [ -z
"$account
" ] ; then
2129 echo
"unable to create local account
"
2134 # Not using dringopreply to ensure $
2 can contain spaces
2135 dbus-send --print-reply --session \
2136 --dest=cx.ring.Ring \
2137 /cx/ring/Ring/ConfigurationManager \
2138 cx.ring.Ring.ConfigurationManager.sendTextMessage \
2139 string:
"$account
" string:
"$
1" \
2140 dict:string:string:
"text/plain
",
"$
2"
2141 </pre
></p
>
2143 <p
>If you want to check it out yourself, visit the
2144 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
2145 more, and install the latest Jami client from Debian Unstable or
2148 <p
>As usual, if you use Bitcoin and want to show your support of my
2149 activities, please send Bitcoin donations to my address
2150 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2155 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
2156 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
2157 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
2158 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
2159 <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
>
2161 <p
>I am happy to report that we finally made it! Norwegian Bokmål
2162 became the first translation published on paper of the new Buster
2163 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
2164 Administrator
's Handbook
</a
>". The print proof reading copy arrived
2165 some days ago, and it looked good, so now the book is approved for
2166 general distribution. This updated paperback edition
<a
2167 href=
"https://debian-handbook.info/get/#norwegian
">is available from
2168 lulu.com
</a
>. The book is also available for download in electronic
2169 form as PDF, EPUB and Mobipocket, and can also be
2170 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
2172 <p
>I am very happy to wrap up this Creative Common licensed project,
2173 which concludes several months of work by several volunteers. The
2174 number of Linux related books published in Norwegian are few, and I
2175 really hope this one will gain many readers, as it is packed with deep
2176 knowledge on Linux and the Debian ecosystem. The book will be
2177 available for various Internet book stores like Amazon and Barnes
&
2178 Noble soon, but I recommend buying
2179 "<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
2180 for Debian-administratoren
</a
>" directly from the source at Lulu.
2182 <p
>As usual, if you use Bitcoin and want to show your support of my
2183 activities, please send Bitcoin donations to my address
2184 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2189 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
2190 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
2191 <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>
2192 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
2193 <description><p
>Thanks to the good work of several volunteers, the updated edition
2194 of the Norwegian translation for
2195 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2196 Handbook
</a
>" is now almost completed. After many months of proof
2197 reading, I consider the proof reading complete enough for us to move
2198 to the next step, and have asked for the print version to be prepared
2199 and sent of to the print on demand service lulu.com. While it is
2200 still not to late if you find any incorrect translations on
2201 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
2202 hosted Weblate service
</a
>, but it will be soon. :) You can check out
2203 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
2204 edition on the web
</a
> until the print edition is ready.
</p
>
2206 <p
>The book will be for sale on lulu.com and various web book stores,
2207 with links available from the web site for the book linked to above.
2208 I hope a lot of readers find it useful.
</p
>
2210 <p
>As usual, if you use Bitcoin and want to show your support of my
2211 activities, please send Bitcoin donations to my address
2212 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2217 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
2218 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
2219 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
2220 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
2221 <description><p
>Three years ago, the first Norwegian Bokmål edition of
2222 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2223 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
2224 new and updated version based on Buster is getting ready. Work on the
2225 updated Norwegian Bokmål edition has been going on for a few months
2226 now, and yesterday, we reached the first mile stone, with
100% of the
2227 texts being translated. A lot of proof reading remains, of course,
2228 but a major step towards a new edition has been taken.
</p
>
2230 <p
>The book is translated by volunteers, and we would love to get some
2231 help with the proof reading. The translation uses
2232 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
2233 hosted Weblate service
</a
>, and we welcome everyone to have a look and
2234 submit improvements and suggestions. There is also a proof readers
2235 PDF available on request, get in touch if you want to help out that
2238 <p
>As usual, if you use Bitcoin and want to show your support of my
2239 activities, please send Bitcoin donations to my address
2240 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2245 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
2246 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
2247 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
2248 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
2249 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
2250 User Group
</a
>, I have the pleasure of receiving the
2251 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
2252 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
2253 several times a year. I rarely have time to read all the articles,
2254 but try to at least skim through them all as there is a lot of nice
2255 knowledge passed on there. I even carry the latest issue with me most
2256 of the time to try to get through all the articles when I have a few
2257 spare minutes.
</p
>
2259 <p
>The other day I came across a nice article titled
2260 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
2261 Secure Socket API: TLS as an Operating System Service
</a
>" with a
2262 marvellous idea I hope can make it all the way into the POSIX standard.
2263 The idea is as simple as it is powerful. By introducing a new
2264 socket() option IPPROTO_TLS to use TLS, and a system wide service to
2265 handle setting up TLS connections, one both make it trivial to add TLS
2266 support to any program currently using the POSIX socket API, and gain
2267 system wide control over certificates, TLS versions and encryption
2268 systems used. Instead of doing this:
</p
>
2270 <p
><blockquote
><pre
>
2271 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
2272 </pre
></blockquote
></p
>
2274 <p
>the program code would be doing this:
<p
>
2276 <p
><blockquote
><pre
>
2277 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
2278 </pre
></blockquote
></p
>
2280 <p
>According to the ;login: article, converting a C program to use TLS
2281 would normally modify only
5-
10 lines in the code, which is amazing
2282 when compared to using for example the OpenSSL API.
</p
>
2284 <p
>The project has set up the
2285 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
2286 web site to spread the idea, and the code for a kernel module and the
2287 associated system daemon is available from two github repositories:
2288 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
2289 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
2290 Unfortunately there is no explicit license information with the code,
2291 so its copyright status is unclear. A
2292 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
2293 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
2295 <p
>I love the idea of extending socket() to gain TLS support, and
2296 understand why it is an advantage to implement this as a kernel module
2297 and system wide service daemon, but can not help to think that it
2298 would be a lot easier to get projects to move to this way of setting
2299 up TLS if it was done with a user space approach where programs
2300 wanting to use this API approach could just link with a wrapper
2303 <p
>I recommend you check out this simple and powerful approach to more
2304 secure network connections. :)
</p
>
2306 <p
>As usual, if you use Bitcoin and want to show your support of my
2307 activities, please send Bitcoin donations to my address
2308 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2313 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
2314 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
2315 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
2316 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
2317 <description><p
>Half a year ago,
2318 <a href=
"https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
2319 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
2320 client
</a
>, capable of peer-to-peer encrypted communication. It
2321 handle both messages, audio and video. It uses distributed hash
2322 tables instead of central infrastructure to connect its users to each
2323 other, which in my book is a plus. I mentioned briefly that it could
2324 also work as a SIP client, which came in handy when the higher
2325 educational sector in Norway started to promote Zoom as its video
2326 conferencing solution. I am reluctant to use the official Zoom client
2327 software, due to their
<a href=
"https://zoom.us/terms
">copyright
2328 license clauses
</a
> prohibiting users to reverse engineer (for example
2329 to check the security) and benchmark it, and thus prefer to connect to
2330 Zoom meetings with free software clients.
</p
>
2332 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
2333 password set on the room. The Jami daemon leak memory like crazy
2334 (approximately
1 GiB a minute) when I am connected to the video
2335 conference, so I had to restart the client every
7-
10 minutes, which
2336 is not great. I tried to get other SIP Linux clients to work
2337 without success, so I decided I would have to live with this wart
2338 until someone managed to fix the leak in the dring code base. But
2339 another problem showed up once the rooms were password protected. I
2340 could not get my dial tone signaling through from Jami to Zoom, and
2341 dial tone signaling is used to enter the password when connecting to
2342 Zoom. I tried a lot of different permutations with my Jami and
2343 Asterisk setup to try to figure out why the signaling did not get
2344 through, only to finally discover that the fundamental problem seem to
2345 be that Zoom is simply not able to receive dial tone signaling when
2346 connecting via SIP. There seem to be nothing wrong with the Jami and
2347 Asterisk end, it is simply broken in the Zoom end. I got help from a
2348 very skilled VoIP engineer figuring out this last part. And being a
2349 very skilled engineer, he was also able to locate a solution for me.
2350 Or to be exact, a workaround that solve my initial problem of
2351 connecting to password protected Zoom rooms using Jami.
</p
>
2353 <p
>So, how do you do this, I am sure you are wondering by now. The
2355 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
2356 from Zoom
</a
>, and it is to modify the SIP address to include the room
2357 password. What is most surprising about this is that the
2358 automatically generated email from Zoom with instructions on how to
2359 connect via SIP do not mention this. The SIP address to use normally
2360 consist of the room ID (a number), an @ character and the IP address
2361 of the Zoom SIP gateway. But Zoom understand a lot more than just the
2362 room ID in front of the at sign. The format is
"<tt
>[Meeting
2363 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
2364 can both enter password, control the layout (full screen, active
2365 presence and gallery) and specify the host key to start the meeting.
2366 The full SIP address entered into Jami to provide the password will
2367 then look like this (all using made up numbers):
</p
>
2369 <p
><blockquote
>
2370 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
2371 </blockquote
></p
>
2373 <p
>Now if only jami would reduce its memory usage, I could even
2374 recommend this setup to others. :)
</p
>
2376 <p
>As usual, if you use Bitcoin and want to show your support of my
2377 activities, please send Bitcoin donations to my address
2378 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2383 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
2384 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
2385 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
2386 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
2387 <description><p
>The curiosity got the better of me when
2388 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
2389 reported
</a
> that New Jersey was desperately looking for
2390 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
2391 and a few days later it was reported that
2392 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
2393 tried to locate COBOL programmers
</a
>.
</p
>
2395 <p
>I thus decided to have a look at free software alternatives to
2396 learn COBOL, and had the pleasure to find
2397 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
2398 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
2399 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
2400 transforming COBOL code to C or C++ before giving it to GCC or Visual
2401 Studio to build binaries.
</p
>
2403 <p
>I managed to get in touch with upstream, and was impressed with the
2404 quick response, and also was happy to see a new Debian maintainer
2405 taking over when the original one recently asked to be replaced. A
2406 new Debian upload was done as recently as yesterday.
</p
>
2408 <p
>Using the Debian package, I was able to follow a simple COBOL
2409 introduction and make and run simple COBOL programs. It was fun to
2410 learn a new programming language. If you want to test for yourself,
2411 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
2412 page
</a
> have a few simple examples to get you startet.
</p
>
2414 <p
>As I do not have much experience with COBOL, I do not know how
2415 standard compliant it is, but it claim to pass most tests from COBOL
2416 test suite, which sound good to me. It is nice to know it is possible
2417 to learn COBOL using software without any usage restrictions, and I am
2418 very happy such nice free software project as this is available. If
2419 you as me is curious about COBOL, check it out.
</p
>
2421 <p
>As usual, if you use Bitcoin and want to show your support of my
2422 activities, please send Bitcoin donations to my address
2423 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2428 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
2429 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
2430 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
2431 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
2432 <description><p
>Some years ago, in
2016, I
2433 <a href=
"https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
2434 for the first time about
</a
> the Ring peer to peer messaging system.
2435 It would provide messaging without any central server coordinating the
2436 system and without requiring all users to register a phone number or
2437 own a mobile phone. Back then, I could not get it to work, and put it
2438 aside until it had seen more development. A few days ago I decided to
2439 give it another try, and am happy to report that this time I am able
2440 to not only send and receive messages, but also place audio and video
2441 calls. But only if UDP is not blocked into your network.
</p
>
2443 <p
>The Ring system changed name earlier this year to
2444 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
2445 tried doing web search for
'ring
' when I discovered it for the first
2446 time, and can only applaud this change as it is impossible to find
2447 something called Ring among the noise of other uses of that word. Now
2448 you can search for
'jami
' and this client and
2449 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
2450 least on duckduckgo.
</p
>
2452 <p
>Jami will by default encrypt messages as well as audio and video
2453 calls, and try to send them directly between the communicating parties
2454 if possible. If this proves impossible (for example if both ends are
2455 behind NAT), it will use a central SIP TURN server maintained by the
2456 Jami project. Jami can also be a normal SIP client. If the SIP
2457 server is unencrypted, the audio and video calls will also be
2458 unencrypted. This is as far as I know the only case where Jami will
2459 do anything without encryption.
</p
>
2461 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
2462 Android, iOS, and Android TV. It is included in Debian already. Jami
2463 also work for those using F-Droid without any Google connections,
2464 while Signal do not.
2465 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
2466 protocol
</a
> is described in the Ring project wiki. The system uses a
2467 distributed hash table (DHT) system (similar to BitTorrent) running
2468 over UDP. On one of the networks I use, I discovered Jami failed to
2469 work. I tracked this down to the fact that incoming UDP packages
2470 going to ports
1-
49999 were blocked, and the DHT would pick a random
2471 port and end up in the low range most of the time. After talking to
2472 the developers, I solved this by enabling the dhtproxy in the
2473 settings, thus using TCP to talk to a central DHT proxy instead of
2475 peering directly with others. I
've been told the developers are
2476 working on allowing DHT to use TCP to avoid this problem. I also ran
2477 into a problem when trying to talk to the version of Ring included in
2478 Debian Stable (Stretch). Apparently the protocol changed between
2479 beta2 and the current version, making these clients incompatible.
2480 Hopefully the protocol will not be made incompatible in the
2483 <p
>It is worth noting that while looking at Jami and its features, I
2484 came across another communication platform I have not tested yet. The
2485 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
2486 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
2487 become the topic of a future blog post.
</p
>
2489 <p
>As usual, if you use Bitcoin and want to show your support of my
2490 activities, please send Bitcoin donations to my address
2491 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2496 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
2497 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
2498 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
2499 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
2500 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
2501 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
2502 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
2503 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
2504 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
2505 nye versjonen kom på nyåret, og ble
2506 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
2507 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
2508 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
2509 måtte justeres, men ikke noe alvorlig. Har oppdatert
2510 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
2511 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
2513 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
2514 å spille for oss som liker slikt. :)
</p
>
2516 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
2517 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
2519 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
2520 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
2525 <title>Debian now got everything you need to program Micro:bit
</title>
2526 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
2527 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
2528 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
2529 <description><p
>I am amazed and very pleased to discover that since a few days ago,
2530 everything you need to program the
<a href=
"https://microbit.org/
">BBC
2531 micro:bit
</a
> is available from the Debian archive. All this is
2532 thanks to the hard work of Nick Morrott and the Debian python
2533 packaging team. The micro:bit project recommend the mu-editor to
2534 program the microcomputer, as this editor will take care of all the
2535 machinery required to injekt/flash micropython alongside the program
2536 into the micro:bit, as long as the pieces are available.
</p
>
2538 <p
>There are three main pieces involved. The first to enter Debian
2540 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
2541 which was accepted into the archive
2019-
01-
12. The next one was
2542 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
2543 showed up
2019-
01-
13. The final and hardest part to to into the
2545 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
2546 which needed to get its build system and dependencies into Debian
2547 before it was accepted
2019-
01-
20. The last one is already in Debian
2548 Unstable and should enter Debian Testing / Buster in three days. This
2549 all allow any user of the micro:bit to get going by simply running
2550 'apt install mu-editor
' when using Testing or Unstable, and once
2551 Buster is released as stable, all the users of Debian stable will be
2552 catered for.
</p
>
2554 <p
>As a minor final touch, I added rules to
2555 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
2556 package
</a
> for recognizing micro:bit and recommend the mu-editor
2557 package. This make sure any user of the isenkram desktop daemon will
2558 get a popup suggesting to install mu-editor then the USB cable from
2559 the micro:bit is inserted for the first time.
</p
>
2561 <p
>This should make it easier to have fun.
</p
>
2563 <p
>As usual, if you use Bitcoin and want to show your support of my
2564 activities, please send Bitcoin donations to my address
2565 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2570 <title>Learn to program with Minetest on Debian
</title>
2571 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
2572 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
2573 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
2574 <description><p
>A fun way to learn how to program
2575 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
2576 instructions in the book
2577 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
2578 with Minecraft
</a
>", which introduces programming in Python to people
2579 who like to play with Minecraft. The book uses a Python library to
2580 talk to a TCP/IP socket with an API accepting build instructions and
2581 providing information about the current players in a Minecraft world.
2582 The TCP/IP API was first created for the Minecraft implementation for
2583 Raspberry Pi, and has since been ported to some server versions of
2584 Minecraft. The book contain recipes for those using Windows, MacOSX
2585 and Raspian. But a little known fact is that you can follow the same
2586 recipes using the free software construction game
2587 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
2589 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
2590 Minetest module implementing the same API
</a
>, making it possible to
2591 use the Python programs coded to talk to Minecraft with Minetest too.
2593 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
2594 this module
</a
> to Debian two weeks ago, and as soon as it clears the
2595 FTP masters NEW queue, learning to program Python with Minetest on
2596 Debian will be a simple
'apt install
' away. The Debian package is
2597 maintained as part of the Debian Games team, and
2598 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
2599 packaging rules
</a
> are currently located under
'unfinished
' on
2602 <p
>You will most likely need to install several of the Minetest
2603 modules in Debian for the examples included with the library to work
2604 well, as there are several blocks used by the example scripts that are
2605 provided via modules in Minetest. Without the required blocks, a
2606 simple stone block is used instead. My initial testing with a analog
2607 clock did not get gold arms as instructed in the python library, but
2608 instead used stone arms.
</p
>
2610 <p
>I tried to find a way to add the API to the desktop version of
2611 Minecraft, but were unable to find any working recipes. The
2612 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
2613 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
2614 working with a standalone Minecraft server setup. Are there any
2615 options to use with the normal desktop version?
</p
>
2617 <p
>As usual, if you use Bitcoin and want to show your support of my
2618 activities, please send Bitcoin donations to my address
2619 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2624 <title>Time for an official MIME type for patches?
</title>
2625 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
2626 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
2627 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
2628 <description><p
>As part of my involvement in
2629 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
2630 archive API project
</a
>, I
've been importing a fairly large lump of
2631 emails into a test instance of the archive to see how well this would
2632 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
2633 notmuch email database
</a
>, all public emails sent to me via
2634 @lists.debian.org, giving me a set of around
216 000 emails to import.
2635 In the process, I had a look at the various attachments included in
2636 these emails, to figure out what to do with attachments, and noticed
2637 that one of the most common attachment formats do not have
2638 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
2639 official MIME type
</a
> registered with IANA/IETF. The output from
2640 diff, ie the input for patch, is on the top
10 list of formats
2641 included in these emails. At the moment people seem to use either
2642 text/x-patch or text/x-diff, but neither is officially registered. It
2643 would be better if one official MIME type were registered and used
2644 everywhere.
</p
>
2646 <p
>To try to get one official MIME type for these files, I
've brought
2648 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
2649 media-types mailing list
</a
>. If you are interested in discussion
2650 which MIME type to use as the official for patch files, or involved in
2651 making software using a MIME type for patches, perhaps you would like
2652 to join the discussion?
</p
>
2654 <p
>As usual, if you use Bitcoin and want to show your support of my
2655 activities, please send Bitcoin donations to my address
2656 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2661 <title>Automatic Google Drive sync using grive in Debian
</title>
2662 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
2663 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
2664 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
2665 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
2666 rescue the remains, I helped set up automatic sync with Google Drive.
2667 I did not find any sensible Debian package handling this
2668 automatically, so I rebuild the grive2 source from
2669 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
2670 task and added a autostart desktop entry and a small shell script to
2671 run in the background while the user is logged in to do the sync.
2672 Here is a sketch of the setup for future reference.
</p
>
2674 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
2675 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
2676 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
2677 to start the sync when the user log in:
</p
>
2679 <p
><blockquote
><pre
>
2681 Name=Google drive autosync
2683 Exec=/home/user/bin/grive-sync
2684 </pre
></blockquote
></p
>
2686 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
2687 ~/googledrive/ with the files in Google Drive.
</p
>
2689 <p
><blockquote
><pre
>
2694 if [
"$syncpid
" ] ; then
2698 trap cleanup EXIT INT QUIT
2699 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
2702 if ! xhost
>/dev/null
2>&1 ; then
2703 echo
"no DISPLAY, exiting as the user probably logged out
"
2706 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
2707 /usr/lib/grive/grive-sync.sh sync googledrive
2710 done
2>&1 | sed
"s%^%$
0:%
"
2711 </pre
></blockquote
></p
>
2713 <p
>Feel free to use the setup if you want. It can be assumed to be
2714 GNU GPL v2 licensed (or any later version, at your leisure), but I
2715 doubt this code is possible to claim copyright on.
</p
>
2717 <p
>As usual, if you use Bitcoin and want to show your support of my
2718 activities, please send Bitcoin donations to my address
2719 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2724 <title>Using the Kodi API to play Youtube videos
</title>
2725 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
2726 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
2727 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
2728 <description><p
>I continue to explore my Kodi installation, and today I wanted to
2729 tell it to play a youtube URL I received in a chat, without having to
2730 insert search terms using the on-screen keyboard. After searching the
2731 web for API access to the Youtube plugin and testing a bit, I managed
2732 to find a recipe that worked. If you got a kodi instance with its API
2733 available from http://kodihost/jsonrpc, you can try the following to
2734 have check out a nice cover band.
</p
>
2736 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
2737 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
2738 "params
": {
"item
": {
"file
":
2739 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
2740 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
2742 <p
>I
've extended kodi-stream program to take a video source as its
2743 first argument. It can now handle direct video links, youtube links
2744 and
'desktop
' to stream my desktop to Kodi. It is almost like a
2745 Chromecast. :)
</p
>
2747 <p
>As usual, if you use Bitcoin and want to show your support of my
2748 activities, please send Bitcoin donations to my address
2749 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2754 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
2755 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
2756 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
2757 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
2758 <description><p
>For a while now, I have looked for a sensible way to share images
2759 with my family using a self hosted solution, as it is unacceptable to
2760 place images from my personal life under the control of strangers
2761 working for data hoarders like Google or Dropbox. The last few days I
2762 have drafted an approach that might work out, and I would like to
2763 share it with you. I would like to publish images on a server under
2764 my control, and point some Internet connected display units using some
2765 free and open standard to the images I published. As my primary
2766 language is not limited to ASCII, I need to store metadata using
2767 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
2768 of reading a RSS feed with image references (aka using the
2769 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
2770 of such frames. In the end I gave up that approach.
</p
>
2772 <p
>Some months ago, I discovered that
2773 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
2774 read images from a RSS feed, and used it to set up a screen saver on
2775 my home info screen, showing images from the Daily images feed from
2776 NASA. This proved to work well. More recently I discovered that
2777 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
2778 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
2779 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
2780 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
2781 screen saver capable of reading a RSS feed with images and news. For
2782 fun, I used it this summer to test Kodi on my parents TV by hooking up
2783 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
2784 screen saver showing selected pictures from my selection.
</p
>
2786 <p
>Armed with motivation and a test photo frame, I set out to generate
2787 a RSS feed for the Kodi instance. I adjusted my
<a
2788 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
2789 /var/www/html/privatepictures/, wrote a small Perl script to extract
2790 title and description metadata from the photo files and generate the
2791 RSS file. I ended up using Perl instead of python, as the
2792 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
2793 tags I ended up using, while python3-exif did not. The relevant EXIF
2794 tags only support ASCII, so I had to find better alternatives. XMP
2795 seem to have the support I need.
</p
>
2797 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
2798 use tags that can be easily added/updated using normal free software
2799 photo managing software. I ended up using the tags set using this
2800 exiftool command, as these tags can also be set using digiKam:
</p
>
2802 <blockquote
><pre
>
2803 exiftool -headline=
'The RSS image title
' \
2804 -description=
'The RSS image description.
' \
2805 -subject+=for-family photo.jpeg
2806 </pre
></blockquote
>
2808 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
2809 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
2810 use the keyword/subject
'for-family
' to flag that the photo should be
2811 shared with my family. Images with this keyword set are located and
2812 copied into my Freedombox for the RSS generating script to find.
</p
>
2814 <p
>Are there better ways to do this? Get in touch if you have better
2815 suggestions.
</p
>
2817 <p
>As usual, if you use Bitcoin and want to show your support of my
2818 activities, please send Bitcoin donations to my address
2819 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2824 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
2825 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
2826 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
2827 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
2828 <description><p
>Last night, I wrote
2829 <a href=
"https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
2830 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
2831 During the day I received valuable feedback, and thanks to the
2832 suggestions I have been able to rewrite the recipe into a much simpler
2833 approach requiring no setup at all. It is a single script that take
2834 care of it all.
</p
>
2836 <p
>This new script uses GStreamer instead of VLC to capture the
2837 desktop and stream it to Kodi. This fixed the video quality issue I
2838 saw initially. It further removes the need to add a m3u file on the
2839 Kodi machine, as it instead connects to
2840 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
2841 Kodi
</a
> and simply ask Kodi to play from the stream created using
2842 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
2843 the script below, run it with the DNS name or IP address of the kodi
2844 server to stream to as the only argument, and watch your screen show
2845 up on the Kodi screen. Note, it depend on multicast on the local
2846 network, so if you need to stream outside the local network, the
2847 script must be modified. Also note, I have no idea if audio work, as
2848 I only care about the picture part.
</p
>
2850 <blockquote
><pre
>
2853 # Stream the Linux desktop view to Kodi. See
2854 # https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
2855 # for backgorund information.
2857 # Make sure the stream is stopped in Kodi and the gstreamer process is
2858 # killed if something go wrong (for example if curl is unable to find the
2859 # kodi server). Do the same when interrupting this script.
2863 params=
"$
3"
2864 curl --silent --header
'Content-Type: application/json
' \
2865 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
2866 "http://$host/jsonrpc
"
2869 if [ -n
"$kodihost
" ] ; then
2870 # Stop the playing when we end
2871 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
2872 jq .result[].playerid)
2873 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
2875 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
2876 kill
"$gstpid
"
2879 trap cleanup EXIT INT
2881 if [ -n
"$
1" ]; then
2892 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
2893 cut -d
" " -f2|head -
1)
2894 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
2895 videoconvert ! queue2 ! \
2896 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
2897 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
2898 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
2899 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
2900 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
2901 > /dev/null
2>&1 &
2904 # Give stream a second to get going
2907 # Ask kodi to start streaming using its JSON-RPC API
2908 kodicmd
"$kodihost
" Player.Open \
2909 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
2911 # wait for gst to end
2912 wait
"$gstpid
"
2913 </pre
></blockquote
>
2915 <p
>I hope you find the approach useful. I know I do.
</p
>
2917 <p
>As usual, if you use Bitcoin and want to show your support of my
2918 activities, please send Bitcoin donations to my address
2919 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2924 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
2925 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
2926 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
2927 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
2928 <description><p
>PS: See
2929 <ahref=
"https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
2930 followup post
</a
> for a even better approach.
</p
>
2932 <p
>A while back, I was asked by a friend how to stream the desktop to
2933 my projector connected to Kodi. I sadly had to admit that I had no
2934 idea, as it was a task I never had tried. Since then, I have been
2935 looking for a way to do so, preferable without much extra software to
2936 install on either side. Today I found a way that seem to kind of
2937 work. Not great, but it is a start.
</p
>
2939 <p
>I had a look at several approaches, for example
2940 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
2941 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
2942 local storage enough to store the stream locally. This is not going
2943 to work well for me, lacking enough free space, and it would
2944 impossible for my friend to get working.
</p
>
2946 <p
>Next, it occurred to me that perhaps I could use VLC to create a
2947 video stream that Kodi could play. Preferably using
2948 broadcast/multicast, to avoid having to change any setup on the Kodi
2949 side when starting such stream. Unfortunately, the only recipe I
2950 could find using multicast used the rtp protocol, and this protocol
2951 seem to not be supported by Kodi.
</p
>
2953 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
2954 have to specify the IP address of the streaming machine in both the
2955 sending command and the file on the Kodi server. But it is showing my
2956 desktop, and thus allow us to have a shared look on the big screen at
2957 the programs I work on.
</p
>
2959 <p
>I did not spend much time investigating codeces. I combined the
2960 rtp and rtsp recipes from
2961 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
2962 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
2963 this working on the desktop/streaming end.
</p
>
2965 <blockquote
><pre
>
2966 vlc screen:// --sout \
2967 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
2968 </pre
></blockquote
>
2970 <p
>I ssh-ed into my Kodi box and created a file like this with the
2971 same IP address:
</p
>
2973 <blockquote
><pre
>
2974 echo rtsp://
192.168.11.4:
8080/test.sdp \
2975 > /storage/videos/screenstream.m3u
2976 </pre
></blockquote
>
2978 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
2979 as I can tell the IP must be hardcoded for this to work. In other
2980 words, if someone elses machine is going to do the steaming, you have
2981 to update screenstream.m3u on the Kodi machine and adjust the vlc
2982 recipe. To get started, locate the file in Kodi and select the m3u
2983 file while the VLC stream is running. The desktop then show up in my
2984 big screen. :)
</p
>
2986 <p
>When using the same technique to stream a video file with audio,
2987 the audio quality is really bad. No idea if the problem is package
2988 loss or bad parameters for the transcode. I do not know VLC nor Kodi
2989 enough to tell.
</p
>
2991 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
2992 succestions and reminded me about an important step. The
"screen:
"
2993 input source is only available once the vlc-plugin-access-extra
2994 package is installed on Debian. Without it, you will see this error
2995 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
2996 for details.
" He further found that it is possible to drop some parts
2997 of the VLC command line to reduce the amount of hardcoded information.
2998 It is also useful to consider using cvlc to avoid having the VLC
2999 window in the desktop view. In sum, this give us this command line on
3002 <blockquote
><pre
>
3003 cvlc screen:// --sout \
3004 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
3005 </pre
></blockquote
>
3007 <p
>and this on the Kodi end
<p
>
3009 <blockquote
><pre
>
3010 echo rtsp://
192.168.11.4:
8080/ \
3011 > /storage/videos/screenstream.m3u
3012 </pre
></blockquote
>
3014 <p
>Still bad image quality, though. But I did discover that streaming
3015 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
3016 audio quality, so I guess the issue is in the input or transcoding
3017 parts, not the rtsp part. I
've tried to change the vb and ab
3018 parameters to use more bandwidth, but it did not make a
3019 difference.
</p
>
3021 <p
>I further received a suggestion from Einar Haraldseid to try using
3022 gstreamer instead of VLC, and this proved to work great! He also
3023 provided me with the trick to get Kodi to use a multicast stream as
3024 its source. By using this monstrous oneliner, I can stream my desktop
3025 with good video quality in reasonable framerate to the
239.255.0.1
3026 multicast address on port
1234:
3028 <blockquote
><pre
>
3029 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
3030 videoconvert ! queue2 ! \
3031 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
3032 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
3033 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
3034 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
3035 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
3036 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
3037 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
3038 </pre
></blockquote
>
3040 <p
>and this on the Kodi end
<p
>
3042 <blockquote
><pre
>
3043 echo udp://@
239.255.0.1:
1234 \
3044 > /storage/videos/screenstream.m3u
3045 </pre
></blockquote
>
3047 <p
>Note the trick to pick a valid pulseaudio source. It might not
3048 pick the one you need. This approach will of course lead to trouble
3049 if more than one source uses the same multicast port and address.
3050 Note the ttl-mc=
1 setting, which limit the multicast packages to the
3051 local network. If the value is increased, your screen will be
3052 broadcasted further, one network
"hop
" for each increase (read up on
3053 multicast to learn more. :)!
</p
>
3055 <p
>Having cracked how to get Kodi to receive multicast streams, I
3056 could use this VLC command to stream to the same multicast address.
3057 The image quality is way better than the rtsp approach, but gstreamer
3058 seem to be doing a better job.
</p
>
3060 <blockquote
><pre
>
3061 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
3062 </pre
></blockquote
>
3064 <p
>As usual, if you use Bitcoin and want to show your support of my
3065 activities, please send Bitcoin donations to my address
3066 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3071 <title>What is the most supported MIME type in Debian in
2018?
</title>
3072 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
3073 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
3074 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
3075 <description><p
>Five years ago,
3076 <a href=
"https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
3077 measured what the most supported MIME type in Debian was
</a
>, by
3078 analysing the desktop files in all packages in the archive. Since
3079 then, the DEP-
11 AppStream system has been put into production, making
3080 the task a lot easier. This made me want to repeat the measurement,
3081 to see how much things changed. Here are the new numbers, for
3082 unstable only this time:
3084 <p
><strong
>Debian Unstable:
</strong
></p
>
3088 ----- -----------------------
3100 30 audio/x-vorbis+ogg
3101 29 image/x-portable-pixmap
3103 27 image/x-portable-bitmap
3105 26 application/x-ogg
3111 <p
>The list was created like this using a sid chroot:
"cat
3112 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
3113 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
3115 <p
>It is interesting to see how image formats have passed text/plain
3116 as the most announced supported MIME type. These days, thanks to the
3117 AppStream system, if you run into a file format you do not know, and
3118 want to figure out which packages support the format, you can find the
3119 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
3120 look up all packages announcing support for this format in their
3121 AppStream metadata (XML or .desktop file) using
"appstreamcli
3122 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
3123 me, want to know which packages support inode/directory, you can get a
3124 list like this:
</p
>
3126 <p
><blockquote
><pre
>
3127 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
3134 Package: doublecmd-common
3136 Package: enlightenment
3156 </pre
></blockquote
></p
>
3158 <p
>Using the same method, I can quickly discover that the Sketchup file
3159 format is not yet supported by any package in Debian:
</p
>
3161 <p
><blockquote
><pre
>
3162 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
3163 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
3165 </pre
></blockquote
></p
>
3167 <p
>Yesterday I used it to figure out which packages support the STL
3D
3170 <p
><blockquote
><pre
>
3171 % appstreamcli what-provides mimetype application/sla|grep Package
3176 </pre
></blockquote
></p
>
3178 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
3180 <p
>As usual, if you use Bitcoin and want to show your support of my
3181 activities, please send Bitcoin donations to my address
3182 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3187 <title>Debian APT upgrade without enough free space on the disk...
</title>
3188 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
3189 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
3190 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
3191 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
3192 for a while, and when I need to update it there is not enough free
3193 space on the disk for apt to do a normal
'apt upgrade
'. I normally
3194 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
3195 upgrade only some of the packages in one batch, until the amount of
3196 packages to download fall below the amount of free space available.
3197 Today, I had about
500 packages to upgrade, and after a while I got
3198 tired of trying to install chunks of packages manually. I concluded
3199 that I did not have the spare hours required to complete the task, and
3200 decided to see if I could automate it. I came up with this small
3201 script which I call
'apt-in-chunks
':
</p
>
3203 <p
><blockquote
><pre
>
3206 # Upgrade packages when the disk is too full to upgrade every
3207 # upgradable package in one lump. Fetching packages to upgrade using
3208 # apt, and then installing using dpkg, to avoid changing the package
3209 # flag for manual/automatic.
3214 if [
"$
1" ]; then
3215 grep -v
"$
1"
3221 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
3222 echo
"Upgrading $p
"
3224 apt install --download-only -y $p
3225 for f in /var/cache/apt/archives/*.deb; do
3226 if [ -e
"$f
" ]; then
3227 dpkg -i /var/cache/apt/archives/*.deb
3232 </pre
></blockquote
></p
>
3234 <p
>The script will extract the list of packages to upgrade, try to
3235 download the packages needed to upgrade one package, install the
3236 downloaded packages using dpkg. The idea is to upgrade packages
3237 without changing the APT mark for the package (ie the one recording of
3238 the package was manually requested or pulled in as a dependency). To
3239 use it, simply run it as root from the command line. If it fail, try
3240 'apt install -f
' to clean up the mess and run the script again. This
3241 might happen if the new packages conflict with one of the old
3242 packages. dpkg is unable to remove, while apt can do this.
</p
>
3244 <p
>It take one option, a package to ignore in the list of packages to
3245 upgrade. The option to ignore a package is there to be able to skip
3246 the packages that are simply too large to unpack. Today this was
3247 'ghc
', but I have run into other large packages causing similar
3248 problems earlier (like TeX).
</p
>
3250 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
3251 alternative ways to handle this. The
"unattended-upgrades
3252 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
3253 each package to upgrade, and then upgrade them in order, smallest set
3254 first. It might be a better option than my above mentioned script.
3255 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
3256 the need for using
"dpkg -i
" in the script above.
</p
>
3258 <p
>As usual, if you use Bitcoin and want to show your support of my
3259 activities, please send Bitcoin donations to my address
3260 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3265 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
3266 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
3267 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
3268 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
3269 <description><p
>A new version of the
3270 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
3271 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
3272 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
3273 useful. It was uploaded the last few days, and the last update will
3274 enter testing tomorrow. See the
3275 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
3276 notes
</a
> for the list of bug fixes and new features. Version
3.2
3277 was announced
6 days ago. We will try to get it into Debian as
3280 <p
>More information related to
3D printing is available on the
3281 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
3282 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
3283 in Debian.
</p
>
3285 <p
>As usual, if you use Bitcoin and want to show your support of my
3286 activities, please send Bitcoin donations to my address
3287 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3292 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
3293 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
3294 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
3295 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
3296 <description><p
>After several months of working and waiting, I am happy to report
3297 that the nice and user friendly
3D printer slicer software Cura just
3298 entered Debian Unstable. It consist of five packages,
3299 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
3300 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
3301 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
3302 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
3303 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
3304 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
3305 two, uranium and cura, entered Unstable yesterday. This should make
3306 it easier for Debian users to print on at least the Ultimaker class of
3307 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
3308 make life easier for at least me. :)
</p
>
3310 <p
>The work to make this happen was done by Gregor Riepl, and I was
3311 happy to assist him in sponsoring the packages. With the introduction
3312 of Cura, Debian is up to three
3D printer slicers at your service,
3313 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
3314 printer, give it a go. :)
</p
>
3316 <p
>The
3D printer software is maintained by the
3D printer Debian
3317 team, flocking together on the
3318 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
3319 mailing list and the
3320 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
3321 IRC channel.
</p
>
3323 <p
>The next step for Cura in Debian is to update the cura package to
3324 version
3.0.3 and then update the entire set of packages to version
3325 3.1.0 which showed up the last few days.
</p
>
3330 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
3331 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
3332 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
3333 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
3334 <description><p
>At my nearby maker space,
3335 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
3336 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
3337 on Windows and MacOS X than Linux, because the software involved had
3338 to be manually compiled and set up on Linux while premade packages
3339 worked out of the box on Windows and MacOS X. I found this annoying,
3340 as the software involved,
3341 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
3342 and should be trivial to get up and running on Linux if someone took
3343 the time to package it for the relevant distributions. I even found
3344 <a href=
"https://bugs.debian.org/
706656">a request for adding into
3345 Debian
</a
> from
2013, which had seem some activity over the years but
3346 never resulted in the software showing up in Debian. So a few days
3347 ago I offered my help to try to improve the situation.
</p
>
3349 <p
>Now I am very happy to see that all the packages required by a
3350 working Cura in Debian are uploaded into Debian and waiting in the NEW
3351 queue for the ftpmasters to have a look. You can track the progress
3353 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
3354 status page for the
3D printer team
</a
>.
</p
>
3356 <p
>The uploaded packages are a bit behind upstream, and was uploaded
3357 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
3358 queue
</a
> while we work up updating the packages to the latest
3359 upstream version.
</p
>
3361 <p
>On a related note, two competitors for Cura, which I found harder
3362 to use and was unable to configure correctly for Ultimaker
2+ in the
3363 short time I spent on it, are already in Debian. If you are looking
3364 for
3D printer
"slicers
" and want something already available in
3366 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
3367 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
3368 The latter is a fork of the former.
</p
>
3370 <p
>As usual, if you use Bitcoin and want to show your support of my
3371 activities, please send Bitcoin donations to my address
3372 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3377 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
3378 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
3379 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
3380 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
3381 <description><p
>Every mobile phone announce its existence over radio to the nearby
3382 mobile cell towers. And this radio chatter is available for anyone
3383 with a radio receiver capable of receiving them. Details about the
3384 mobile phones with very good accuracy is of course collected by the
3385 phone companies, but this is not the topic of this blog post. The
3386 mobile phone radio chatter make it possible to figure out when a cell
3387 phone is nearby, as it include the SIM card ID (IMSI). By paying
3388 attention over time, one can see when a phone arrive and when it leave
3389 an area. I believe it would be nice to make this information more
3390 available to the general public, to make more people aware of how
3391 their phones are announcing their whereabouts to anyone that care to
3394 <p
>I am very happy to report that we managed to get something
3395 visualizing this information up and running for
3396 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
3397 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
3398 library. The solution is based on the
3399 <a href=
"https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
3400 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
3401 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
3402 Sone from the Computer Science department of the University of
3403 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
3404 IMSIs) as dots in a web browser graph, with lines to the dot
3405 representing mobile base station it is talking to. It was working in
3406 the lab yesterday, and was moved into place this morning.
</p
>
3408 <p
>We set up a fairly powerful desktop machine using Debian
3409 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
3410 connected and visualize the visible cell phone towers using an
3411 <a href=
"https://github.com/marlow925/hopglass
">English version of
3412 Hopglass
</a
>. A fairly powerfull machine is needed as the
3413 grgsm_livemon_headless processes from
3414 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
3415 the radio signal to data packages is quite CPU intensive.
</p
>
3417 <p
>The frequencies to listen to, are identified using a slightly
3418 patched scan-and-livemon (to set the --args values for each receiver),
3419 and the Hopglass data is generated using the
3420 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
3421 in my meshviewer-output branch
</a
>. For some reason we could not get
3422 more than four SDRs working. There is also a geographical map trying
3423 to show the location of the base stations, but I believe their
3424 coordinates are hardcoded to some random location in Germany, I
3425 believe. The code should be replaced with code to look up location in
3426 a text file, a sqlite database or one of the online databases
3428 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
3429 issue for the topic
</a
>.
3431 <p
>If this sound interesting, visit the stand at the festival!
</p
>
3436 <title>Easier recipe to observe the cell phones around you
</title>
3437 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
3438 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
3439 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
3440 <description><p
>A little more than a month ago I wrote
3441 <a href=
"https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
3442 to observe the SIM card ID (aka IMSI number) of mobile phones talking
3443 to nearby mobile phone base stations using Debian GNU/Linux and a
3444 cheap USB software defined radio
</a
>, and thus being able to pinpoint
3445 the location of people and equipment (like cars and trains) with an
3446 accuracy of a few kilometer. Since then we have worked to make the
3447 procedure even simpler, and it is now possible to do this without any
3448 manual frequency tuning and without building your own packages.
</p
>
3450 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
3451 package is now included in Debian testing and unstable, and the
3452 IMSI-catcher code no longer require root access to fetch and decode
3453 the GSM data collected using gr-gsm.
</p
>
3455 <p
>Here is an updated recipe, using packages built by Debian and a git
3456 clone of two python scripts:
</p
>
3460 <li
>Start with a Debian machine running the Buster version (aka
3461 testing).
</li
>
3463 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
3464 python-scapy
</tt
>' as root to install required packages.
</li
>
3466 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
3467 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
3469 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
3471 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
3472 scan-and-livemon
</tt
>' to locate the frequency of nearby base
3473 stations and start listening for GSM packages on one of them.
</li
>
3475 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
3476 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
3480 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
3481 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
3482 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
3483 work with RTL
8232 and other similar USB radio receivers you can get
3485 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
3486 from ebay
</a
>), so for now the solution is to scan using the RTL radio
3487 and only use HackRF for fetching GSM data.
</p
>
3489 <p
>As far as I can tell, a cell phone only show up on one of the
3490 frequencies at the time, so if you are going to track and count every
3491 cell phone around you, you need to listen to all the frequencies used.
3492 To listen to several frequencies, use the --numrecv argument to
3493 scan-and-livemon to use several receivers. Further, I am not sure if
3494 phones using
3G or
4G will show as talking GSM to base stations, so
3495 this approach might not see all phones around you. I typically see
3496 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
3498 <p
>I
've tried to run the scanner on a
3499 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
3500 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
3501 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
3502 stdout, I am told there it is caused by a buffer overflow between the
3503 radio and GNU Radio, caused by the program being unable to read the
3504 GSM data fast enough. If you see a stream of
'O
's from the terminal
3505 where you started scan-and-livemon, you need a give the process more
3506 CPU power. Perhaps someone are able to optimize the code to a point
3507 where it become possible to set up RPi3 based GSM sniffers? I tried
3508 using Raspbian instead of Debian, but there seem to be something wrong
3509 with GNU Radio on raspbian, causing glibc to abort().
</p
>
3514 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
3515 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
3516 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
3517 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
3518 <description><p
>On friday, I came across an interesting article in the Norwegian
3519 web based ICT news magazine digi.no on
3520 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
3521 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
3522 DVB-T software defined radios. The article refered to instructions
3523 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
3524 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
3526 <p
>The instructions said to use Ubuntu, install pip using apt (to
3527 bypass apt), use pip to install pybombs (to bypass both apt and pip),
3528 and the ask pybombs to fetch and build everything you need from
3529 scratch. I wanted to see if I could do the same on the most recent
3530 Debian packages, but this did not work because pybombs tried to build
3531 stuff that no longer build with the most recent openssl library or
3532 some other version skew problem. While trying to get this recipe
3533 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
3534 and the only piece of software dependency missing in Debian was the
3535 gr-gsm package. I also found out that the lead upstream developer of
3536 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
3537 Debian packages provided in an Ubuntu PPA repository. All I needed to
3538 do was to dget the Debian source package and built it.
</p
>
3540 <p
>The IMSI collector is a python script listening for packages on the
3541 loopback network device and printing to the terminal some specific GSM
3542 packages with IMSI numbers in them. The code is fairly short and easy
3543 to understand. The reason this work is because gr-gsm include a tool
3544 to read GSM data from a software defined radio like a DVB-T USB stick
3545 and other software defined radios, decode them and inject them into a
3546 network device on your Linux machine (using the loopback device by
3547 default). This proved to work just fine, and I
've been testing the
3548 collector for a few days now.
</p
>
3550 <p
>The updated and simpler recipe is thus to
</p
>
3554 <li
>start with a Debian machine running Stretch or newer,
</li
>
3556 <li
>build and install the gr-gsm package available from
3557 <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
>
3559 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
3561 <li
>run grgsm_livemon and adjust the frequency until the terminal
3562 where it was started is filled with a stream of text (meaning you
3563 found a GSM station).
</li
>
3565 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
3569 <p
>To make it even easier in the future to get this sniffer up and
3570 running, I decided to package
3571 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
3572 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
3573 #
871055</a
>), and the package was uploaded into the NEW queue today.
3574 Luckily the gnuradio maintainer has promised to help me, as I do not
3575 know much about gnuradio stuff yet.
</p
>
3577 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
3578 commercial tools like
3579 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
3580 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
3581 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
3582 Stingray
</a
>, but I hope the existance of cheap alternatives can make
3583 more people realise how their whereabouts when carrying a cell phone
3584 is easily tracked. Seeing the data flow on the screen, realizing that
3585 I live close to a police station and knowing that the police is also
3586 wearing cell phones, I wonder how hard it would be for criminals to
3587 track the position of the police officers to discover when there are
3588 police near by, or for foreign military forces to track the location
3589 of the Norwegian military forces, or for anyone to track the location
3590 of government officials...
</p
>
3592 <p
>It is worth noting that the data reported by the IMSI-catcher
3593 script mentioned above is only a fraction of the data broadcasted on
3594 the GSM network. It will only collect one frequency at the time,
3595 while a typical phone will be using several frequencies, and not all
3596 phones will be using the frequencies tracked by the grgsm_livemod
3597 program. Also, there is a lot of radio chatter being ignored by the
3598 simple_IMSI-catcher script, which would be collected by extending the
3599 parser code. I wonder if gr-gsm can be set up to listen to more than
3600 one frequency?
</p
>
3605 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
3606 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
3607 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
3608 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
3609 <description><p align=
"center
"><img align=
"center
" src=
"https://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
3611 <p
>I finally received a copy of the Norwegian Bokmål edition of
3612 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
3613 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
3614 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
3615 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
3616 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
3617 price. The book is also available for download in electronic form as
3618 PDF, EPUB and Mobipocket, as can be
3619 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
3620 as a web page
</a
>.
</p
>
3622 <p
>This is the second book I publish (the first was the book
3623 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
3625 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
3626 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
3628 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
3629 Bokmål
</a
>), and I am very excited to finally wrap up this
3631 "<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
3632 for Debian-administratoren
</a
>" will be well received.
</p
>
3637 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
3638 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
3639 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
3640 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
3641 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
3642 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
3643 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
3644 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
3645 på om den fri oversetterløsningen
3646 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
3647 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
3649 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
3652 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
3653 rolle og muligheter til å håndtere internasjonale utfordringer, som
3654 for eksempel flykningekrisen.
</p
>
3656 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
3657 på temaet:
</p
>
3659 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
3660 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
3665 <p
>Dette oversetter Apertium slik:
</p
>
3668 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
3669 andre aktørar og høve til å handtera internasjonale utfordringar, som
3670 til dømes *flykningekrisen.
</p
>
3672 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
3676 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
3677 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
3682 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
3683 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
3684 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
3685 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
3686 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
3687 det er kanskje flisespikking. Det understreker vel bare at det alltid
3688 trengs korrekturlesning etter automatisk oversettelse.
</p
>
3693 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
3694 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
3695 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
3696 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
3697 <description><p
>Over the years, administrating thousand of NFS mounting linux
3698 computers at the time, I often needed a way to detect if the machine
3699 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
3700 file or directory affected by the hang, the process (and possibly the
3701 shell) will hang too. So you want to be able to detect this without
3702 risking the detection process getting stuck too. It has not been
3703 obvious how to do this. When the hang has lasted a while, it is
3704 possible to find messages like these in dmesg:
</p
>
3706 <p
><blockquote
>
3707 nfs: server nfsserver not responding, still trying
3708 <br
>nfs: server nfsserver OK
3709 </blockquote
></p
>
3711 <p
>It is hard to know if the hang is still going on, and it is hard to
3712 be sure looking in dmesg is going to work. If there are lots of other
3713 messages in dmesg the lines might have rotated out of site before they
3714 are noticed.
</p
>
3716 <p
>While reading through the nfs client implementation in linux kernel
3717 code, I came across some statistics that seem to give a way to detect
3718 it. The om_timeouts sunrpc value in the kernel will increase every
3719 time the above log entry is inserted into dmesg. And after digging a
3720 bit further, I discovered that this value show up in
3721 /proc/self/mountstats on Linux.
</p
>
3723 <p
>The mountstats content seem to be shared between files using the
3724 same file system context, so it is enough to check one of the
3725 mountstats files to get the state of the mount point for the machine.
3726 I assume this will not show lazy umounted NFS points, nor NFS mount
3727 points in a different process context (ie with a different filesystem
3728 view), but that does not worry me.
</p
>
3730 <p
>The content for a NFS mount point look similar to this:
</p
>
3732 <p
><blockquote
><pre
>
3734 device /dev/mapper/Debian-var mounted on /var with fstype ext3
3735 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
3736 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
3738 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
3739 sec: flavor=
1,pseudoflavor=
1
3740 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
3741 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
3742 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
3743 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
3745 NULL:
0 0 0 0 0 0 0 0
3746 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
3747 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
3748 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
3749 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
3750 READLINK:
125 125 0 20472 18620 0 1112 1118
3751 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
3752 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
3753 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
3754 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
3755 SYMLINK:
903 903 0 233428 245488 6 5865 5917
3756 MKNOD:
80 80 0 20148 21760 0 299 304
3757 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
3758 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
3759 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
3760 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
3761 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
3762 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
3763 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
3764 FSINFO:
2 2 0 232 328 0 1 1
3765 PATHCONF:
1 1 0 116 140 0 0 0
3766 COMMIT:
0 0 0 0 0 0 0 0
3768 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
3770 </pre
></blockquote
></p
>
3772 <p
>The key number to look at is the third number in the per-op list.
3773 It is the number of NFS timeouts experiences per file system
3774 operation. Here
22 write timeouts and
5 access timeouts. If these
3775 numbers are increasing, I believe the machine is experiencing NFS
3776 hang. Unfortunately the timeout value do not start to increase right
3777 away. The NFS operations need to time out first, and this can take a
3778 while. The exact timeout value depend on the setup. For example the
3779 defaults for TCP and UDP mount points are quite different, and the
3780 timeout value is affected by the soft, hard, timeo and retrans NFS
3781 mount options.
</p
>
3783 <p
>The only way I have been able to get working on Debian and RedHat
3784 Enterprise Linux for getting the timeout count is to peek in /proc/.
3786 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
3787 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
3788 command can be used to get these timeout values. But this do not work
3789 on Linux, as far as I can tell. I
3790 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
3791 but have not seen any replies yet.
</p
>
3793 <p
>Is there a better way to figure out if a Linux NFS client is
3794 experiencing NFS hangs? Is there a way to detect which processes are
3795 affected? Is there a way to get the NFS mount going quickly once the
3796 network problem causing the NFS hang has been cleared? I would very
3797 much welcome some clues, as we regularly run into NFS hangs.
</p
>
3802 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
3803 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
3804 <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>
3805 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
3806 <description><p
>For almost a year now, we have been working on making a Norwegian
3807 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
3808 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
3809 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
3810 we are working on the proof reading to ensure consistent language and
3811 use of correct computer science terms. The plan is to make the book
3812 available on paper, as well as in electronic form. For that to
3813 happen, the proof reading must be completed and all the figures need
3814 to be translated. If you want to help out, get in touch.
</p
>
3816 <p
><a href=
"https://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
3818 fresh PDF edition
</a
> in A4 format (the final book will have smaller
3819 pages) of the book created every morning is available for
3820 proofreading. If you find any errors, please
3821 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
3822 Weblate and correct the error
</a
>. The
3823 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
3824 of the translation including figures
</a
> is a useful source for those
3825 provide Norwegian bokmål screen shots and figures.
</p
>
3830 <title>Unlimited randomness with the ChaosKey?
</title>
3831 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
3832 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
3833 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
3834 <description><p
>A few days ago I ordered a small batch of
3835 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
3836 USB dongle for generating entropy created by Bdale Garbee and Keith
3837 Packard. Yesterday it arrived, and I am very happy to report that it
3838 work great! According to its designers, to get it to work out of the
3839 box, you need the Linux kernel version
4.1 or later. I tested on a
3840 Debian Stretch machine (kernel version
4.9), and there it worked just
3841 fine, increasing the available entropy very quickly. I wrote a small
3842 test oneliner to test. It first print the current entropy level,
3843 drain /dev/random, and then print the entropy level for five seconds.
3844 Here is the situation without the ChaosKey inserted:
</p
>
3846 <blockquote
><pre
>
3847 % cat /proc/sys/kernel/random/entropy_avail; \
3848 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3849 for n in $(seq
1 5); do \
3850 cat /proc/sys/kernel/random/entropy_avail; \
3856 28 byte kopiert,
0,
000264565 s,
106 kB/s
3863 </pre
></blockquote
>
3865 <p
>The entropy level increases by
3-
4 every second. In such case any
3866 application requiring random bits (like a HTTPS enabled web server)
3867 will halt and wait for more entrpy. And here is the situation with
3868 the ChaosKey inserted:
</p
>
3870 <blockquote
><pre
>
3871 % cat /proc/sys/kernel/random/entropy_avail; \
3872 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3873 for n in $(seq
1 5); do \
3874 cat /proc/sys/kernel/random/entropy_avail; \
3880 104 byte kopiert,
0,
000487647 s,
213 kB/s
3887 </pre
></blockquote
>
3889 <p
>Quite the difference. :) I bought a few more than I need, in case
3890 someone want to buy one here in Norway. :)
</p
>
3892 <p
>Update: The dongle was presented at Debconf last year. You might
3893 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
3894 recording illuminating
</a
>. It explains exactly what the source of
3895 randomness is, if you are unable to spot it from the schema drawing
3896 available from the ChaosKey web site linked at the start of this blog
3902 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
3903 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
3904 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
3905 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
3906 <description><p
>Did you ever wonder where the web trafic really flow to reach the
3907 web servers, and who own the network equipment it is flowing through?
3908 It is possible to get a glimpse of this from using traceroute, but it
3909 is hard to find all the details. Many years ago, I wrote a system to
3910 map the Norwegian Internet (trying to figure out if our plans for a
3911 network game service would get low enough latency, and who we needed
3912 to talk to about setting up game servers close to the users. Back
3913 then I used traceroute output from many locations (I asked my friends
3914 to run a script and send me their traceroute output) to create the
3915 graph and the map. The output from traceroute typically look like
3918 <p
><pre
>
3919 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
3920 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
3921 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
3922 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
3923 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
3924 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
3925 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
3926 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
3930 </pre
></p
>
3932 <p
>This show the DNS names and IP addresses of (at least some of the)
3933 network equipment involved in getting the data traffic from me to the
3934 www.stortinget.no server, and how long it took in milliseconds for a
3935 package to reach the equipment and return to me. Three packages are
3936 sent, and some times the packages do not follow the same path. This
3937 is shown for hop
5, where three different IP addresses replied to the
3938 traceroute request.
</p
>
3940 <p
>There are many ways to measure trace routes. Other good traceroute
3941 implementations I use are traceroute (using ICMP packages) mtr (can do
3942 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
3943 traceroute and a lot of other capabilities). All of them are easily
3944 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
3946 <p
>This time around, I wanted to know the geographic location of
3947 different route points, to visualize how visiting a web page spread
3948 information about the visit to a lot of servers around the globe. The
3949 background is that a web site today often will ask the browser to get
3950 from many servers the parts (for example HTML, JSON, fonts,
3951 JavaScript, CSS, video) required to display the content. This will
3952 leak information about the visit to those controlling these servers
3953 and anyone able to peek at the data traffic passing by (like your ISP,
3954 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
3956 <p
>Lets pick an example, the Norwegian parliament web site
3957 www.stortinget.no. It is read daily by all members of parliament and
3958 their staff, as well as political journalists, activits and many other
3959 citizens of Norway. A visit to the www.stortinget.no web site will
3960 ask your browser to contact
8 other servers: ajax.googleapis.com,
3961 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3962 stats.g.doubleclick.net, www.google-analytics.com,
3963 www.googletagmanager.com and www.netigate.se. I extracted this by
3964 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
3965 Stortinget web page and tell me all the URLs PhantomJS downloaded to
3966 render the page (in HAR format using
3967 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
3968 netsniff example
</a
>. I am very grateful to Gorm for showing me how
3969 to do this). My goal is to visualize network traces to all IP
3970 addresses behind these DNS names, do show where visitors personal
3971 information is spread when visiting the page.
</p
>
3973 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
3974 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
>
3976 <p
>When I had a look around for options, I could not find any good
3977 free software tools to do this, and decided I needed my own traceroute
3978 wrapper outputting KML based on locations looked up using GeoIP. KML
3979 is easy to work with and easy to generate, and understood by several
3980 of the GIS tools I have available. I got good help from by NUUG
3981 colleague Anders Einar with this, and the result can be seen in
3982 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
3983 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
3984 free GeoIP databases I could find (and the for-pay databases my
3985 friends had access to) is not up to the task. The IP addresses of
3986 central Internet infrastructure would typically be placed near the
3987 controlling companies main office, and not where the router is really
3988 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
3989 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
3991 <p align=
"center
"><a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
3992 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
>
3994 <p
>I also had a look at the visual traceroute graph created by
3995 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
3996 showing IP network ownership (aka AS owner) for the IP address in
3998 <a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
3999 graph display a lot of useful information about the traceroute in SVG
4000 format
</a
>, and give a good indication on who control the network
4001 equipment involved, but it do not include geolocation. This graph
4002 make it possible to see the information is made available at least for
4003 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
4004 3 Communications and NetDNA.
</p
>
4006 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
4007 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
>
4009 <p
>In the process, I came across the
4010 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
4011 Salim Gasmi. Its methology of combining guesses based on DNS names,
4012 various location databases and finally use latecy times to rule out
4013 candidate locations seemed to do a very good job of guessing correct
4014 geolocation. But it could only do one trace at the time, did not have
4015 a sensor in Norway and did not make the geolocations easily available
4016 for postprocessing. So I contacted the developer and asked if he
4017 would be willing to share the code (he refused until he had time to
4018 clean it up), but he was interested in providing the geolocations in a
4019 machine readable format, and willing to set up a sensor in Norway. So
4020 since yesterday, it is possible to run traces from Norway in this
4021 service thanks to a sensor node set up by
4022 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
4023 trace in KML format for further processing.
</p
>
4025 <p align=
"center
"><a href=
"https://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
4026 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
>
4028 <p
>Here we can see a lot of trafic passes Sweden on its way to
4029 Denmark, Germany, Holland and Ireland. Plenty of places where the
4030 Snowden confirmations verified the traffic is read by various actors
4031 without your best interest as their top priority.
</p
>
4033 <p
>Combining KML files is trivial using a text editor, so I could loop
4034 over all the hosts behind the urls imported by www.stortinget.no and
4035 ask for the KML file from GeoTraceroute, and create a combined KML
4036 file with all the traces (unfortunately only one of the IP addresses
4037 behind the DNS name is traced this time. To get them all, one would
4038 have to request traces using IP number instead of DNS names from
4039 GeoTraceroute). That might be the next step in this project.
</p
>
4041 <p
>Armed with these tools, I find it a lot easier to figure out where
4042 the IP traffic moves and who control the boxes involved in moving it.
4043 And every time the link crosses for example the Swedish border, we can
4044 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
4045 Britain and NSA in USA and cables around the globe. (Hm, what should
4046 we tell them? :) Keep that in mind if you ever send anything
4047 unencrypted over the Internet.
</p
>
4049 <p
>PS: KML files are drawn using
4050 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
4051 Rublev
<a/
>, as it was less cluttered than the local Linux application
4052 Marble. There are heaps of other options too.
</p
>
4054 <p
>As usual, if you use Bitcoin and want to show your support of my
4055 activities, please send Bitcoin donations to my address
4056 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4061 <title>Appstream just learned how to map hardware to packages too!
</title>
4062 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
4063 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
4064 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
4065 <description><p
>I received a very nice Christmas present today. As my regular
4066 readers probably know, I have been working on the
4067 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
4068 system
</a
> for many years. The goal of the Isenkram system is to make
4069 it easier for users to figure out what to install to get a given piece
4070 of hardware to work in Debian, and a key part of this system is a way
4071 to map hardware to packages. Isenkram have its own mapping database,
4072 and also uses data provided by each package using the AppStream
4073 metadata format. And today,
4074 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
4075 Debian learned to look up hardware the same way Isenkram is doing it,
4076 ie using fnmatch():
</p
>
4078 <p
><pre
>
4079 % appstreamcli what-provides modalias \
4080 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
4081 Identifier: pymissile [generic]
4083 Summary: Control original Striker USB Missile Launcher
4085 % appstreamcli what-provides modalias usb:v0694p0002d0000
4086 Identifier: libnxt [generic]
4088 Summary: utility library for talking to the LEGO Mindstorms NXT brick
4091 Identifier: t2n [generic]
4093 Summary: Simple command-line tool for Lego NXT
4096 Identifier: python-nxt [generic]
4098 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
4101 Identifier: nbc [generic]
4103 Summary: C compiler for LEGO Mindstorms NXT bricks
4106 </pre
></p
>
4108 <p
>A similar query can be done using the combined AppStream and
4109 Isenkram databases using the isenkram-lookup tool:
</p
>
4111 <p
><pre
>
4112 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
4114 % isenkram-lookup usb:v0694p0002d0000
4120 </pre
></p
>
4122 <p
>You can find modalias values relevant for your machine using
4123 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
4125 <p
>If you want to make this system a success and help Debian users
4126 make the most of the hardware they have, please help
4127 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
4128 metadata for your package following the guidelines
</a
> documented in
4129 the wiki. So far only
11 packages provide such information, among the
4130 several hundred hardware specific packages in Debian. The Isenkram
4131 database on the other hand contain
101 packages, mostly related to USB
4132 dongles. Most of the packages with hardware mapping in AppStream are
4133 LEGO Mindstorms related, because I have, as part of my involvement in
4134 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
4135 team
</a
> given priority to making sure LEGO users get proposed the
4136 complete set of packages in Debian for that particular hardware. The
4137 team also got a nice Christmas present today. The
4138 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
4139 package
</a
> made it into Debian. With this package in place, it is
4140 now possible to use the LEGO Mindstorms NXT unit with only free
4141 software, as the nxt-firmware package contain the source and firmware
4142 binaries for the NXT brick.
</p
>
4144 <p
>As usual, if you use Bitcoin and want to show your support of my
4145 activities, please send Bitcoin donations to my address
4146 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4151 <title>Isenkram updated with a lot more hardware-package mappings
</title>
4152 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
4153 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
4154 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
4155 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
4156 system
</a
> I wrote two years ago to make it easier in Debian to find
4157 and install packages to get your hardware dongles to work, is still
4158 going strong. It is a system to look up the hardware present on or
4159 connected to the current system, and map the hardware to Debian
4160 packages. It can either be done using the tools in isenkram-cli or
4161 using the user space daemon in the isenkram package. The latter will
4162 notify you, when inserting new hardware, about what packages to
4163 install to get the dongle working. It will even provide a button to
4164 click on to ask packagekit to install the packages.
</p
>
4166 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
4168 <p
><pre
>
4185 </pre
></p
>
4187 <p
>It can also list the firware package providing firmware requested
4188 by the load kernel modules, which in my case is an empty list because
4189 I have all the firmware my machine need:
4191 <p
><pre
>
4192 % /usr/sbin/isenkram-autoinstall-firmware -l
4193 info: did not find any firmware files requested by loaded kernel modules. exiting
4195 </pre
></p
>
4197 <p
>The last few days I had a look at several of the around
250
4198 packages in Debian with udev rules. These seem like good candidates
4199 to install when a given hardware dongle is inserted, and I found
4200 several that should be proposed by isenkram. I have not had time to
4201 check all of them, but am happy to report that now there are
97
4202 packages packages mapped to hardware by Isenkram.
11 of these
4203 packages provide hardware mapping using AppStream, while the rest are
4204 listed in the modaliases file provided in isenkram.
</p
>
4206 <p
>These are the packages with hardware mappings at the moment. The
4207 <strong
>marked packages
</strong
> are also announcing their hardware
4208 support using AppStream, for everyone to use:
</p
>
4210 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
4211 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
4212 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
4213 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
4214 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
4215 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
4216 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
4217 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
4218 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
4219 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
4220 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
4221 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
4222 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
4223 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
4224 pcscd, pidgin-blinklight, printer-driver-splix,
4225 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
4226 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
4227 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
4228 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
4229 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
4230 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
4231 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
4232 xserver-xorg-video-vmware, yubikey-personalization and
4233 zd1211-firmware
</p
>
4235 <p
>If you know of other packages, please let me know with a wishlist
4236 bug report against the isenkram-cli package, and ask the package
4238 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
4239 metadata according to the guidelines
</a
> to provide the information
4240 for everyone. In time, I hope to get rid of the isenkram specific
4241 hardware mapping and depend exclusively on AppStream.
</p
>
4243 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
4244 much hardware, and suggest that the package with with any ethernet
4245 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
4246 the details. I hope the maintainer find time to address it soon. In
4247 the mean time I provide an override in isenkram.
</p
>
4252 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
4253 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
4254 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
4255 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
4256 <description><p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
4258 <p
>In my early years, I played
4259 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
4260 Elite
</a
> on my PC. I spent many months trading and fighting in
4261 space, and reached the
'elite
' fighting status before I moved on. The
4262 original Elite game was available on Commodore
64 and the IBM PC
4263 edition I played had a
64 KB executable. I am still impressed today
4264 that the authors managed to squeeze both a
3D engine and details about
4265 more than
2000 planet systems across
7 galaxies into a binary so
4268 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
4269 software game Oolite inspired by Elite
</a
> for a while, but did not
4270 really have time to test it properly until a few days ago. It was
4271 great to discover that my old knowledge about trading routes were
4272 still valid. But my fighting and flying abilities were gone, so I had
4273 to retrain to be able to dock on a space station. And I am still not
4274 able to make much resistance when I am attacked by pirates, so I
4275 bougth and mounted the most powerful laser in the rear to be able to
4276 put up at least some resistance while fleeing for my life. :)
</p
>
4278 <p
>When playing Elite in the late eighties, I had to discover
4279 everything on my own, and I had long lists of prices seen on different
4280 planets to be able to decide where to trade what. This time I had the
4282 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
4283 where information about each planet is easily available with common
4284 price ranges and suggested trading routes. This improved my ability
4285 to earn money and I have been able to earn enough to buy a lot of
4286 useful equipent in a few days. I believe I originally played for
4287 months before I could get a docking computer, while now I could get it
4288 after less then a week.
</p
>
4290 <p
>If you like science fiction and dreamed of a life as a vagabond in
4291 space, you should try out Oolite. It is available for Linux, MacOSX
4292 and Windows, and is included in Debian and derivatives since
2011.
</p
>
4294 <p
>As usual, if you use Bitcoin and want to show your support of my
4295 activities, please send Bitcoin donations to my address
4296 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4301 <title>Quicker Debian installations using eatmydata
</title>
4302 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
4303 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
4304 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
4305 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
4306 installation system, observing how using
4307 <a href=
"https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
4308 could speed up the installation
</a
> quite a bit. My testing measured
4309 speedup around
20-
40 percent for Debian Edu, where we install around
4310 1000 packages from within the installer. The eatmydata package
4311 provide a way to disable/delay file system flushing. This is a bit
4312 risky in the general case, as files that should be stored on disk will
4313 stay only in memory a bit longer than expected, causing problems if a
4314 machine crashes at an inconvenient time. But for an installation, if
4315 the machine crashes during installation the process is normally
4316 restarted, and avoiding disk operations as much as possible to speed
4317 up the process make perfect sense.
4319 <p
>I added code in the Debian Edu specific installation code to enable
4320 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
4321 but did not have time to push it any further. But a few months ago I
4322 picked it up again and worked with the libeatmydata package maintainer
4323 Mattia Rizzolo to make it easier for everyone to get this installation
4324 speedup in Debian. Thanks to our cooperation There is now an
4325 eatmydata-udeb package in Debian testing and unstable, and simply
4326 enabling/installing it in debian-installer (d-i) is enough to get the
4327 quicker installations. It can be enabled using preseeding. The
4328 following untested kernel argument should do the trick:
</p
>
4330 <blockquote
><pre
>
4331 preseed/early_command=
"anna-install eatmydata-udeb
"
4332 </pre
></blockquote
>
4334 <p
>This should ask d-i to install the package inside the d-i
4335 environment early in the installation sequence. Having it installed
4336 in d-i in turn will make sure the relevant scripts are called just
4337 after debootstrap filled /target/ with the freshly installed Debian
4338 system to configure apt to run dpkg with eatmydata. This is enough to
4339 speed up the installation process. There is a proposal to
4340 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
4341 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
4342 tested its impact.
</p
>
4348 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
4349 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
4350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
4351 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
4352 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
4353 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
4354 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
4355 elever over det ganske land skal levere inn hvert år. Det mange ikke
4356 vet er at selv om de kommersielle alternativene
4357 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
4358 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
4359 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
4360 utmerket fri programvarealternativ som kan. Oversetterverktøyet
4361 Apertium har støtte for en rekke språkkombinasjoner, og takket være
4362 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
4363 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
4364 nynorsk, og få den automatoversatt til det andre skriftspråket.
4365 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
4366 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
4367 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
4368 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
4369 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
4370 teksten din i webskjemaet der.
4372 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
4373 teknologien kan du enten installere pakken
4374 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
4375 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
4376 api.apertium.org. Se
4377 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
4378 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
4379 denne teksten som ble skrevet på bokmål over maskinoversatt til
4384 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
4385 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
4386 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
4387 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
4388 veit er at sjølv om dei kommersielle alternativa
4389 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
4390 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
4391 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
4392 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
4393 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
4394 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
4395 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
4396 nynorsk, og få den *automatoversatt til det andre skriftspråket.
4397 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
4398 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
4399 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
4400 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
4401 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
4402 teksta di i *webskjemaet der.
4404 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
4405 teknologien kan du anten installera pakken
4406 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
4407 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
4408 *api.*apertium.org. Sjå
4409 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
4410 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
4411 for denne teksta som vart skreva på bokmål over *maskinoversatt til
4417 <title>Coz profiler for multi-threaded software is now in Debian
</title>
4418 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
4419 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
4420 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
4421 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
4422 profiler able to run benchmarking experiments on the instrumented
4423 multi-threaded program, finally
4424 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
4425 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
4427 <a href=
"https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
4428 blogged about the coz tool
</a
> in August working with upstream to make
4429 it suitable for Debian. There are still issues with clang
4430 compatibility, inline assembly only working x86 and minimized
4431 JavaScript libraries.
</p
>
4433 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
4435 <p
><blockquote
>
4436 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
4437 </blockquote
></p
>
4439 <p
>This will produce a profile.coz file in the current working
4440 directory with the profiling information. This is then given to a
4441 JavaScript application provided in the package and available from
4442 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
4443 To start the local copy, invoke it in a browser like this:
</p
>
4445 <p
><blockquote
>
4446 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
4447 </blockquote
></p
>
4449 <p
>See the project home page and the
4450 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
4451 ;login: article on Coz
</a
> for more information on how it is
4457 <title>My own self balancing Lego Segway
</title>
4458 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
4459 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
4460 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
4461 <description><p
>A while back I received a Gyro sensor for the NXT
4462 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
4463 present. It had been on my wishlist for a while, because I wanted to
4464 build a Segway like balancing lego robot. I had already built
4465 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
4466 robot
</a
> with the kids, using the light/color sensor included in the
4467 NXT kit as the balance sensor, but it was not working very well. It
4468 could balance for a while, but was very sensitive to the light
4469 condition in the room and the reflective properties of the surface and
4470 would fall over after a short while. I wanted something more robust,
4472 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
4473 gyro sensor from HiTechnic
</a
> I believed would solve it on my
4474 wishlist for some years before it suddenly showed up as a gift from my
4475 loved ones. :)
</p
>
4477 <p
>Unfortunately I have not had time to sit down and play with it
4478 since then. But that changed some days ago, when I was searching for
4479 lego segway information and came across a recipe from HiTechnic for
4481 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
4482 HTWay
</a
>, a segway like balancing robot. Build instructions and
4483 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
4484 code
</a
> was included, so it was just a question of putting it all
4485 together. And thanks to the great work of many Debian developers, the
4486 compiler needed to build the source for the NXT is already included in
4487 Debian, so I was read to go in less than an hour. The resulting robot
4488 do not look very impressive in its simplicity:
</p
>
4490 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
4492 <p
>Because I lack the infrared sensor used to control the robot in the
4493 design from HiTechnic, I had to comment out the last task
4494 (taskControl). I simply placed /* and */ around it get the program
4495 working without that sensor present. Now it balances just fine until
4496 the battery status run low:
</p
>
4498 <p align=
"center
"><video width=
"70%
" controls=
"true
">
4499 <source src=
"https://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
4500 </video
></p
>
4502 <p
>Now we would like to teach it how to follow a line and take remote
4503 control instructions using the included Bluetooth receiver in the NXT.
</p
>
4505 <p
>If you, like me, love LEGO and want to make sure we find the tools
4506 they need to work with LEGO in Debian and all our derivative
4507 distributions like Ubuntu, check out
4508 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
4509 project page
</a
> and join the Debian LEGO team. Personally I own a
4510 RCX and NXT controller (no EV3), and would like to make sure the
4511 Debian tools needed to program the systems I own work as they
4517 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
4518 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
4519 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
4520 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
4521 <description><p
>In July
4522 <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
4523 wrote how to get the Signal Chrome/Chromium app working
</a
> without
4524 the ability to receive SMS messages (aka without a cell phone). It is
4525 time to share some experiences and provide an updated setup.
</p
>
4527 <p
>The Signal app have worked fine for several months now, and I use
4528 it regularly to chat with my loved ones. I had a major snag at the
4529 end of my summer vacation, when the the app completely forgot my
4530 setup, identity and keys. The reason behind this major mess was
4531 running out of disk space. To avoid that ever happening again I have
4532 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
4533 roll back to an earlier version if the files are wiped by mistake. I
4534 had to use it once after introducing the git backup. When rolling
4535 back to an earlier version, one need to use the
'reset session
' option
4536 in Signal to get going, and notify the people you talk with about the
4537 problem. I assume there is some sequence number tracking in the
4538 protocol to detect rollback attacks. The git repository is rather big
4539 (
674 MiB so far), but I have not tried to figure out if some of the
4540 content can be added to a .gitignore file due to lack of spare
4543 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
4544 make it impossible to send messages using Signal. I could still
4545 receive them, but had to patch the code with a new timestamp to send.
4546 I believe the timeout is added by the developers to force people to
4547 upgrade to the latest version of the app, even when there is no
4548 protocol changes, to reduce the version skew among the user base and
4549 thus try to keep the number of support requests down.
</p
>
4551 <p
>Since my original recipe, the Signal source code changed slightly,
4552 making the old patch fail to apply cleanly. Below is an updated
4553 patch, including the shell wrapper I use to start Signal. The
4554 original version required a new user to locate the JavaScript console
4555 and call a function from there. I got help from a friend with more
4556 JavaScript knowledge than me to modify the code to provide a GUI
4557 button instead. This mean that to get started you just need to run
4558 the wrapper and click the
'Register without mobile phone
' to get going
4559 now. I
've also modified the timeout code to always set it to
90 days
4560 in the future, to avoid having to patch the code regularly.
</p
>
4562 <p
>So, the updated recipe for Debian Jessie:
</p
>
4566 <li
>First, install required packages to get the source code and the
4567 browser you need. Signal only work with Chrome/Chromium, as far as I
4568 know, so you need to install it.
4571 apt install git tor chromium
4572 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4573 </pre
></li
>
4575 <li
>Modify the source code using command listed in the the patch
4576 block below.
</li
>
4578 <li
>Start Signal using the run-signal-app wrapper (for example using
4579 <tt
>`pwd`/run-signal-app
</tt
>).
4581 <li
>Click on the
'Register without mobile phone
', will in a phone
4582 number you can receive calls to the next minute, receive the
4583 verification code and enter it into the form field and press
4584 'Register
'. Note, the phone number you use will be user Signal
4585 username, ie the way others can find you on Signal.
</li
>
4587 <li
>You can now use Signal to contact others. Note, new contacts do
4588 not show up in the contact list until you restart Signal, and there is
4589 no way to assign names to Contacts. There is also no way to create or
4590 update chat groups. I suspect this is because the web app do not have
4591 a associated contact database.
</li
>
4595 <p
>I am still a bit uneasy about using Signal, because of the way its
4596 main author moxie0 reject federation and accept dependencies to major
4597 corporations like Google (part of the code is fetched from Google) and
4598 Amazon (the central coordination point is owned by Amazon). See for
4600 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
4601 LibreSignal issue tracker
</a
> for a thread documenting the authors
4602 view on these issues. But the network effect is strong in this case,
4603 and several of the people I want to communicate with already use
4604 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
4605 once it
<a href=
"https://bugs.debian.org/
830265">work on my
4606 laptop
</a
>? It already work on Windows and Android, and is included
4607 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
4608 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
4609 working on Debian Stable.
</p
>
4611 <p
>Anyway, this is the patch I apply to the Signal code to get it
4612 working. It switch to the production servers, disable to timeout,
4613 make registration easier and add the shell wrapper:
</p
>
4616 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
4617 diff --git a/js/background.js b/js/background.js
4618 index
24b4c1d.
.579345f
100644
4619 --- a/js/background.js
4620 +++ b/js/background.js
4625 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
4626 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
4627 var SERVER_PORTS = [
80,
4433,
8443];
4628 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
4629 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
4630 var messageReceiver;
4631 window.getSocketStatus = function() {
4632 if (messageReceiver) {
4633 diff --git a/js/expire.js b/js/expire.js
4634 index
639aeae..beb91c3
100644
4639 'use strict
';
4640 - var BUILD_EXPIRATION =
0;
4641 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
4643 window.extension = window.extension || {};
4645 diff --git a/js/views/install_view.js b/js/views/install_view.js
4646 index
7816f4f.
.1d6233b
100644
4647 --- a/js/views/install_view.js
4648 +++ b/js/views/install_view.js
4651 'click .step1
': this.selectStep.bind(this,
1),
4652 'click .step2
': this.selectStep.bind(this,
2),
4653 -
'click .step3
': this.selectStep.bind(this,
3)
4654 +
'click .step3
': this.selectStep.bind(this,
3),
4655 +
'click .callreg
': function() { extension.install(
'standalone
') },
4658 clearQR: function() {
4659 diff --git a/options.html b/options.html
4660 index dc0f28e.
.8d709f6
100644
4664 &lt;div class=
'nav
'>
4665 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
4666 &lt;p
>{{ installTagline }}
&lt;/p
>
4667 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
4668 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
4669 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
4672 &lt;span class=
'dot step1 selected
'>&lt;/span
>
4673 &lt;span class=
'dot step2
'>&lt;/span
>
4674 &lt;span class=
'dot step3
'>&lt;/span
>
4675 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
4676 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
4682 +userdata=
"`pwd`/userdata
"
4683 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
4684 + (cd $userdata
&& git init)
4686 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
4688 + --proxy-server=
"socks://localhost:
9050" \
4689 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
4691 chmod a+rx run-signal-app
4694 <p
>As usual, if you use Bitcoin and want to show your support of my
4695 activities, please send Bitcoin donations to my address
4696 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4701 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
4702 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
4703 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
4704 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
4705 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
4706 system
</a
> provide a practical and easy way to figure out which
4707 packages support the hardware in a given machine. The command line
4708 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
4709 convenient way to list and install packages relevant for the current
4710 hardware during system installation, both user space packages and
4711 firmware packages. The GUI background daemon on the other hand provide
4712 a pop-up proposing to install packages when a new dongle is inserted
4713 while using the computer. For example, if you plug in a smart card
4714 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
4715 that package isn
't already installed, and if you plug in a USB video
4716 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
4717 cheese is currently missing. This already work just fine.
</p
>
4719 <p
>But Isenkram depend on a database mapping from hardware IDs to
4720 package names. When I started no such database existed in Debian, so
4721 I made my own data set and included it with the isenkram package and
4722 made isenkram fetch the latest version of this database from git using
4723 http. This way the isenkram users would get updated package proposals
4724 as soon as I learned more about hardware related packages.
</p
>
4726 <p
>The hardware is identified using modalias strings. The modalias
4727 design is from the Linux kernel where most hardware descriptors are
4728 made available as a strings that can be matched using filename style
4729 globbing. It handle USB, PCI, DMI and a lot of other hardware related
4730 identifiers.
</p
>
4732 <p
>The downside to the Isenkram specific database is that there is no
4733 information about relevant distribution / Debian version, making
4734 isenkram propose obsolete packages too. But along came AppStream, a
4735 cross distribution mechanism to store and collect metadata about
4736 software packages. When I heard about the proposal, I contacted the
4737 people involved and suggested to add a hardware matching rule using
4738 modalias strings in the specification, to be able to use AppStream for
4739 mapping hardware to packages. This idea was accepted and AppStream is
4740 now a great way for a package to announce the hardware it support in a
4741 distribution neutral way. I wrote
4742 <a href=
"https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
4743 recipe on how to add such meta-information
</a
> in a blog post last
4744 December. If you have a hardware related package in Debian, please
4745 announce the relevant hardware IDs using AppStream.
</p
>
4747 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
4748 RCX or NXT unit, announce this support using AppStream. The effect is
4749 that when you insert such LEGO robot controller into your Debian
4750 machine, Isenkram will propose to install the packages needed to get
4751 it working. The intention is that this should allow the local user to
4752 start programming his robot controller right away without having to
4753 guess what packages to use or which permissions to fix.
</p
>
4755 <p
>But when I sat down with my son the other day to program our NXT
4756 unit using his Debian Stretch computer, I discovered something
4757 annoying. The local console user (ie my son) did not get access to
4758 the USB device for programming the unit. This used to work, but no
4759 longer in Jessie and Stretch. After some investigation and asking
4760 around on #debian-devel, I discovered that this was because udev had
4761 changed the mechanism used to grant access to local devices. The
4762 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
4763 no longer applied, because LDAP users no longer was added to the
4764 plugdev group during login. Michael Biebl told me that this method
4765 was obsolete and the new method used ACLs instead. This was good
4766 news, as the plugdev mechanism is a mess when using a remote user
4767 directory like LDAP. Using ACLs would make sure a user lost device
4768 access when she logged out, even if the user left behind a background
4769 process which would retain the plugdev membership with the ConsoleKit
4770 setup. Armed with this knowledge I moved on to fix the access problem
4771 for the LEGO Mindstorms related packages.
</p
>
4773 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
4774 applied directly for a device, or is applied in
4775 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
4776 LEGO Mindstorms udev rules did not have a class, I decided to add the
4777 tag directly in the udev rules files included in the packages. Here
4778 is one example. For the nqc C compiler for the RCX, the
4779 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
4781 <p
><pre
>
4782 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
4783 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
4784 </pre
></p
>
4786 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
4787 packages using plugdev in their /lib/udev/rules.d/ files should be
4788 changed to use this tag (either directly or indirectly via
4789 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
4790 to detect this?
</p
>
4792 <p
>I
've been unable to find good documentation on the uaccess feature.
4793 It is unclear to me if the uaccess tag is an internal implementation
4794 detail like the udev-acl tag used by
4795 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
4796 indirect method is the preferred way. Michael
4797 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
4798 documentation from the systemd project
</a
> and I hope it will make
4799 this clearer. For now I use the generic classes when they exist and
4800 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
4801 directly if no such class exist.
</p
>
4803 <p
>To learn more about the isenkram system, please check out
4804 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4805 blog posts tagged isenkram
</a
>.
</p
>
4807 <p
>To help out making life for LEGO constructors in Debian easier,
4808 please join us on our IRC channel
4809 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
4810 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
4811 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
4812 list is not yet created, but we are working on it. :)
</p
>
4814 <p
>As usual, if you use Bitcoin and want to show your support of my
4815 activities, please send Bitcoin donations to my address
4816 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4821 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
4822 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
4823 <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>
4824 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
4825 <description><p
>In April we
4826 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
4827 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
4828 how to set up and administrate a Debian system. Today I am happy to
4829 report that the first draft is now publicly available. You can find
4830 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
4831 Administrator
's Handbook page
</a
> (under Other languages). The first
4832 eight chapters have a first draft translation, and we are working on
4833 proofreading the content. If you want to help out, please start
4835 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4836 hosted weblate project page
</a
>, and get in touch using
4837 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4838 translators mailing list
</a
>. Please also check out
4839 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4840 contributors
</a
>. A good way to contribute is to proofread the text
4841 and update weblate if you find errors.
</p
>
4843 <p
>Our goal is still to make the Norwegian book available on paper as well as
4844 electronic form.
</p
>
4849 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
4850 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
4851 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
4852 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
4853 <description><p
>This summer, I read a great article
4854 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
4855 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
4856 how to profile multi-threaded programs. It presented a system for
4857 profiling software by running experiences in the running program,
4858 testing how run time performance is affected by
"speeding up
" parts of
4859 the code to various degrees compared to a normal run. It does this by
4860 slowing down parallel threads while the
"faster up
" code is running
4861 and measure how this affect processing time. The processing time is
4862 measured using probes inserted into the code, either using progress
4863 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
4864 can also measure unmodified code by measuring complete the program
4865 runtime and running the program several times instead.
</p
>
4867 <p
>The project and presentation was so inspiring that I would like to
4868 get the system into Debian. I
4869 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
4870 a WNPP request for it
</a
> and contacted upstream to try to make the
4871 system ready for Debian by sending patches. The build process need to
4872 be changed a bit to avoid running
'git clone
' to get dependencies, and
4873 to include the JavaScript web page used to visualize the collected
4874 profiling information included in the source package.
4875 But I expect that should work out fairly soon.
</p
>
4877 <p
>The way the system work is fairly simple. To run an coz experiment
4878 on a binary with debug symbols available, start the program like this:
4880 <p
><blockquote
><pre
>
4881 coz run --- program-to-run
4882 </pre
></blockquote
></p
>
4884 <p
>This will create a text file profile.coz with the instrumentation
4885 information. To show what part of the code affect the performance
4886 most, use a web browser and either point it to
4887 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
4888 or use the copy from git (in the gh-pages branch). Check out this web
4889 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
4890 profiling more useful you include
&lt;coz.h
&gt; and insert the
4891 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
4892 code, rebuild and run the profiler. This allow coz to do more
4893 targeted experiments.
</p
>
4895 <p
>A video published by ACM
4896 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
4897 Coz profiler
</a
> is available from Youtube. There is also a paper
4898 from the
25th Symposium on Operating Systems Principles available
4900 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
4901 finding code that counts with causal profiling
</a
>.
</p
>
4903 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
4904 for Coz is available from github. It will only build with clang
4906 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
4907 feature missing in GCC
</a
>, but I
've submitted
4908 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
4909 it
</a
> and hope it will be included in the upstream source soon.
</p
>
4911 <p
>Please get in touch if you, like me, would like to see this piece
4912 of software in Debian. I would very much like some help with the
4913 packaging effort, as I lack the in depth knowledge on how to package
4914 C++ libraries.
</p
>
4919 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
4920 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
4921 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
4922 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
4923 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
4924 to be a slight challenge. Here is the recipe if I ever need to do it
4925 again. It all started by me wanting to try the recipe to set up
4926 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
4927 hardened Android installation
</a
> from the Tor project blog on a
4928 device I had access to. It is a old mobile phone with a broken
4929 microphone The initial idea had been to just
4930 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
4931 CyanogenMod on it
</a
>, but did not quite find time to start on it
4932 until a few days ago.
</p
>
4934 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
4935 loader (press volume down and power at the same time), (
2) select
4936 'fastboot
' before (
3) connecting the device via USB to a Linux
4937 machine, (
4) request the device identifier token by running
'fastboot
4938 oem get_identifier_token
', (
5) request the device unlocking key using
4939 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
4940 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
4942 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
4943 or newer, and the device I was working on had
2.00.0027. This
4944 apparently can be easily fixed by downloading a Windows program and
4945 running it on your Windows machine, if you accept the terms Microsoft
4946 require you to accept to use Windows - which I do not. So I had to
4947 come up with a different approach. I got a lot of help from AndyCap
4948 on #nuug, and would not have been able to get this working without
4951 <p
>First I needed to extract the hboot firmware from
4952 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
4953 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
4954 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
4955 project named unruu
</a
> using libunshield. The unshield tool did not
4956 recognise the file format, but unruu worked and extracted rom.zip,
4957 containing the new hboot firmware and a text file describing which
4958 devices it would work for.
</p
>
4960 <p
>Next, I needed to get the new firmware into the device. For this I
4961 followed some instructions
4962 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
4963 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
4964 machine with Debian testing:
</p
>
4966 <p
><pre
>
4967 adb reboot-bootloader
4968 fastboot oem rebootRUU
4969 fastboot flash zip rom.zip
4970 fastboot flash zip rom.zip
4972 </pre
></p
>
4974 <p
>The flash command apparently need to be done twice to take effect,
4975 as the first is just preparations and the second one do the flashing.
4976 The adb command is just to get to the boot loader menu, so turning the
4977 device on while holding volume down and the power button should work
4980 <p
>With the new hboot version in place I could start following the
4981 instructions on the HTC developer web site. I got the device token
4982 like this:
</p
>
4984 <p
><pre
>
4985 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
4988 <p
>And once I got the unlock code via email, I could use it like
4991 <p
><pre
>
4992 fastboot flash unlocktoken Unlock_code.bin
4993 </pre
></p
>
4995 <p
>And with that final step in place, the phone was unlocked and I
4996 could start stuffing the software of my own choosing into the device.
4997 So far I only inserted a replacement recovery image to wipe the phone
4998 before I start. We will see what happen next. Perhaps I should
4999 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
5004 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
5005 <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>
5006 <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>
5007 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
5008 <description><p
>For a while now, I have wanted to test
5009 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
5010 said to provide end to end encrypted communication and several of my
5011 friends and family are already using it. As I by choice do not own a
5012 mobile phone, this proved to be harder than expected. And I wanted to
5013 have the source of the client and know that it was the code used on my
5014 machine. But yesterday I managed to get it working. I used the
5015 Github source, compared it to the source in
5016 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
5017 Signal Chrome app
</a
> available from the Chrome web store, applied
5018 patches to use the production Signal servers, started the app and
5019 asked for the hidden
"register without a smart phone
" form. Here is
5020 the recipe how I did it.
</p
>
5022 <p
>First, I fetched the Signal desktop source from Github, using
5025 git clone https://github.com/WhisperSystems/Signal-Desktop.git
5028 <p
>Next, I patched the source to use the production servers, to be
5029 able to talk to other Signal users:
</p
>
5032 cat
&lt;
&lt;EOF | patch -p0
5033 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
5034 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
5035 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
5040 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
5041 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
5042 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
5043 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
5044 var messageReceiver;
5045 window.getSocketStatus = function() {
5046 if (messageReceiver) {
5047 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
5048 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
5049 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
5052 'use strict
';
5053 - var BUILD_EXPIRATION =
0;
5054 + var BUILD_EXPIRATION =
1474492690000;
5056 window.extension = window.extension || {};
5061 <p
>The first part is changing the servers, and the second is updating
5062 an expiration timestamp. This timestamp need to be updated regularly.
5063 It is set
90 days in the future by the build process (Gruntfile.js).
5064 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
5066 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
5067 script to launch Signal in Chromium.
</p
>
5074 --proxy-server=
"socks://localhost:
9050" \
5075 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
5078 <p
> The script start the app and configure Chromium to use the Tor
5079 SOCKS5 proxy to make sure those controlling the Signal servers (today
5080 Amazon and Whisper Systems) as well as those listening on the lines
5081 will have a harder time location my laptop based on the Signal
5082 connections if they use source IP address.
</p
>
5084 <p
>When the script starts, one need to follow the instructions under
5085 "Standalone Registration
" in the CONTRIBUTING.md file in the git
5086 repository. I right clicked on the Signal window to get up the
5087 Chromium debugging tool, visited the
'Console
' tab and wrote
5088 'extension.install(
"standalone
")
' on the console prompt to get the
5089 registration form. Then I entered by land line phone number and
5090 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
5091 repeated the verification code three times. After entering the number
5092 into the verification code field in the form, I could start using
5093 Signal from my laptop.
5095 <p
>As far as I can tell, The Signal app will leak who is talking to
5096 whom and thus who know who to those controlling the central server,
5097 but such leakage is hard to avoid with a centrally controlled server
5098 setup. It is something to keep in mind when using Signal - the
5099 content of your chats are harder to intercept, but the meta data
5100 exposing your contact network is available to people you do not know.
5101 So better than many options, but not great. And sadly the usage is
5102 connected to my land line, thus allowing those controlling the server
5103 to associate it to my home and person. I would prefer it if only
5104 those I knew could tell who I was on Signal. There are options
5105 avoiding such information leakage, but most of my friends are not
5106 using them, so I am stuck with Signal for now.
</p
>
5108 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
5110 <a href=
"https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
5111 and updated recipe for using the Signal app without a mobile
5112 phone
</a
>.
</p
>
5117 <title>The new
"best
" multimedia player in Debian?
</title>
5118 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
5119 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
5120 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
5121 <description><p
>When I set out a few weeks ago to figure out
5122 <a href=
"https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
5123 multimedia player in Debian claimed to support most file formats /
5124 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
5125 the various players claimed support for. The range was from
55 to
130
5126 MIME types. I suspect most media formats are supported by all
5127 players, but this is not really reflected in the MimeTypes values in
5128 their desktop files. There are probably also some bogus MIME types
5129 listed, but it is hard to identify which one this is.
</p
>
5131 <p
>Anyway, in the mean time I got in touch with upstream for some of
5132 the players suggesting to add more MIME types to their desktop files,
5133 and decided to spend some time myself improving the situation for my
5134 favorite media player VLC. The fixes for VLC entered Debian unstable
5135 yesterday. The complete list of MIME types can be seen on the
5136 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
5137 player MIME type support status
</a
> Debian wiki page.
</p
>
5139 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
5140 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
5141 kmplayer. I am sure some of the other players desktop files support
5142 several of the formats currently listed as working only with vlc,
5143 toten and parole.
</p
>
5145 <p
>A sad observation is that only
14 MIME types are listed as
5146 supported by all the tested multimedia players in Debian in their
5147 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
5148 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
5149 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
5150 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
5151 it sad that video/ogg and video/webm is not supported by all the media
5152 players in Debian. As far as I can tell, all of them can handle both
5158 <title>A program should be able to open its own files on Linux
</title>
5159 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
5160 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
5161 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
5162 <description><p
>Many years ago, when koffice was fresh and with few users, I
5163 decided to test its presentation tool when making the slides for a
5164 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
5165 wrote the first draft of the slides, saved the result and went to bed
5166 the day before I would give the talk. The next day I took a plane to
5167 the location where the meeting should take place, and on the plane I
5168 started up koffice again to polish the talk a bit, only to discover
5169 that kpresenter refused to load its own data file. I cursed a bit and
5170 started making the slides again from memory, to have something to
5171 present when I arrived. I tested that the saved files could be
5172 loaded, and the day seemed to be rescued. I continued to polish the
5173 slides until I suddenly discovered that the saved file could no longer
5174 be loaded into kpresenter. In the end I had to rewrite the slides
5175 three times, condensing the content until the talk became shorter and
5176 shorter. After the talk I was able to pinpoint the problem
&ndash;
5177 kpresenter wrote inline images in a way itself could not understand.
5178 Eventually that bug was fixed and kpresenter ended up being a great
5179 program to make slides. The point I
'm trying to make is that we
5180 expect a program to be able to load its own data files, and it is
5181 embarrassing to its developers if it can
't.
</p
>
5183 <p
>Did you ever experience a program failing to load its own data
5184 files from the desktop file browser? It is not a uncommon problem. A
5185 while back I discovered that the screencast recorder
5186 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
5187 browser would refuse to open. No video player claimed to understand
5188 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
5189 returning the application/ogg MIME type, which no video player I had
5190 installed listed as a MIME type they would understand. I asked for
5191 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
5192 behavour
</a
> and use the MIME type video/ogg instead. I also asked
5193 several video players to add video/ogg to their desktop files, to give
5194 the file browser an idea what to do about Ogg Theora files. After a
5195 while, the desktop file browsers in Debian started to handle the
5196 output from gtk-recordmydesktop properly.
</p
>
5198 <p
>But history repeats itself. A few days ago I tested the music
5199 system Rosegarden again, and I discovered that the KDE and xfce file
5200 browsers did not know what to do with the Rosegarden project files
5201 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
5202 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
5203 included in the next upload. To increase the chance of me remembering
5204 how to fix the problem next time some program fail to load its files
5205 from the file browser, here are some notes on how to fix it.
</p
>
5207 <p
>The file browsers in Debian in general operates on MIME types.
5208 There are two sources for the MIME type of a given file. The output from
5209 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
5210 shared MIME type registry (under /usr/share/mime/). The file MIME
5211 type is mapped to programs supporting the MIME type, and this
5212 information is collected from
5213 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
5214 desktop files
</a
> available in /usr/share/applications/. If there is
5215 one desktop file claiming support for the MIME type of the file, it is
5216 activated when asking to open a given file. If there are more, one
5217 can normally select which one to use by right-clicking on the file and
5218 selecting the wanted one using
'Open with
' or similar. In general
5219 this work well. But it depend on each program picking a good MIME
5221 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
5222 MIME type registered with IANA
</a
>), file and/or the shared MIME
5223 registry recognizing the file and the desktop file to list the MIME
5224 type in its list of supported MIME types.
</p
>
5226 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
5227 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
5228 Shared MIME database
</a
> look like this:
</p
>
5230 <p
><blockquote
><pre
>
5231 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
5232 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
5233 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
5234 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
5235 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
5236 &lt;glob pattern=
"*.rg
"/
&gt;
5237 &lt;/mime-type
&gt;
5238 &lt;/mime-info
&gt;
5239 </pre
></blockquote
></p
>
5241 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
5242 (it is a gzipped XML file). Note, it is much better to use an
5243 official MIME type registered with IANA than it is to make up ones own
5244 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
5246 <p
>The desktop file of the rosegarden program failed to list
5247 audio/x-rosegarden in its list of supported MIME types, causing the
5248 file browsers to have no idea what to do with *.rg files:
</p
>
5250 <p
><blockquote
><pre
>
5251 % grep Mime /usr/share/applications/rosegarden.desktop
5252 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
5253 X-KDE-NativeMimeType=audio/x-rosegarden-composition
5255 </pre
></blockquote
></p
>
5257 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
5258 MimeType= line.
</p
>
5260 <p
>If you run into a file which fail to open the correct program when
5261 selected from the file browser, please check out the output from
5262 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
5263 MIME type is registered somewhere under /usr/share/mime/ and check
5264 that some desktop file under /usr/share/applications/ is claiming
5265 support for this MIME type. If not, please report a bug to have it
5271 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
5272 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
5273 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
5274 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
5275 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
5276 system
</a
> is a user-focused solution in Debian for handling hardware
5277 related packages. The idea is to have a database of mappings between
5278 hardware and packages, and pop up a dialog suggesting for the user to
5279 install the packages to use a given hardware dongle. Some use cases
5280 are when you insert a Yubikey, it proposes to install the software
5281 needed to control it; when you insert a braille reader list it
5282 proposes to install the packages needed to send text to the reader;
5283 and when you insert a ColorHug screen calibrator it suggests to
5284 install the driver for it. The system work well, and even have a few
5285 command line tools to install firmware packages and packages for the
5286 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
5288 <p
>The system was initially written using aptdaemon, because I found
5289 good documentation and example code on how to use it. But aptdaemon
5290 is going away and is generally being replaced by
5291 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
5292 so Isenkram needed a rewrite. And today, thanks to the great patch
5293 from my college Sunil Mohan Adapa in the FreedomBox project, the
5294 rewrite finally took place. I
've just uploaded a new version of
5295 Isenkram into Debian Unstable with the patch included, and the default
5296 for the background daemon is now to use PackageKit. To check it out,
5297 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
5298 and see if it is recognised.
</p
>
5300 <p
>If you want to know what kind of packages isenkram would propose for
5301 the machine it is running on, you can check out the isenkram-lookup
5302 program. This is what it look like on a Thinkpad X230:
</p
>
5304 <p
><blockquote
><pre
>
5320 </pre
></blockquote
></p
>
5322 <p
>The hardware mappings come from several places. The preferred way
5323 is for packages to announce their hardware support using
5324 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
5325 cross distribution appstream system
</a
>.
5327 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
5328 blog posts about isenkram
</a
> to learn how to do that.
</p
>
5333 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
5334 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
5335 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
5336 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
5337 <description><p
>Yesterday I updated the
5338 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
5339 package in Debian
</a
> with a few patches sent to me by skilled and
5340 enterprising users. There were some nice user and visible changes.
5341 First of all, both desktop menu entries now work. A design flaw in
5342 one of the script made the history graph fail to show up (its PNG was
5343 dumped in ~/.xsession-errors) if no controlling TTY was available.
5344 The script worked when called from the command line, but not when
5345 called from the desktop menu. I changed this to look for a DISPLAY
5346 variable or a TTY before deciding where to draw the graph, and now the
5347 graph window pop up as expected.
</p
>
5349 <p
>The next new feature is a discharge rate estimator in one of the
5350 graphs (the one showing the last few hours). New is also the user of
5351 colours showing charging in blue and discharge in red. The percentages
5352 of this graph is relative to last full charge, not battery design
5355 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
5357 <p
>The other graph show the entire history of the collected battery
5358 statistics, comparing it to the design capacity of the battery to
5359 visualise how the battery life time get shorter over time. The red
5360 line in this graph is what the previous graph considers
100 percent:
5362 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
5364 <p
>In this graph you can see that I only charge the battery to
80
5365 percent of last full capacity, and how the capacity of the battery is
5366 shrinking. :(
</p
>
5368 <p
>The last new feature is in the collector, which now will handle
5369 more hardware models. On some hardware, Linux power supply
5370 information is stored in /sys/class/power_supply/ACAD/, while the
5371 collector previously only looked in /sys/class/power_supply/AC/. Now
5372 both are checked to figure if there is power connected to the
5375 <p
>If you are interested in how your laptop battery is doing, please
5377 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
5378 in Debian unstable, or rebuild it on Jessie to get it working on
5379 Debian stable. :) The upstream source is available from
<a
5380 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5381 Patches are very welcome.
</p
>
5383 <p
>As usual, if you use Bitcoin and want to show your support of my
5384 activities, please send Bitcoin donations to my address
5385 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5390 <title>Debian now with ZFS on Linux included
</title>
5391 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
5392 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
5393 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
5394 <description><p
>Today, after many years of hard work from many people,
5395 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
5396 Debian. The package status can be seen on
5397 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
5398 for zfs-linux
</a
>. and
5399 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
5400 team status page
</a
>. If you want to help out, please join us.
5401 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
5402 source code
</a
> is available via git on Alioth. It would also be
5403 great if you could help out with
5404 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
5405 it is an important piece of the puzzle to get ZFS working.
</p
>
5410 <title>What is the best multimedia player in Debian?
</title>
5411 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
5412 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
5413 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
5414 <description><p
><strong
>Where I set out to figure out which multimedia player in
5415 Debian claim support for most file formats.
</strong
></p
>
5417 <p
>A few years ago, I had a look at the media support for Browser
5418 plugins in Debian, to get an idea which plugins to include in Debian
5419 Edu. I created a script to extract the set of supported MIME types
5420 for each plugin, and used this to find out which multimedia browser
5421 plugin supported most file formats / media types.
5422 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
5423 result
</a
> can still be seen on the Debian wiki, even though it have
5424 not been updated for a while. But browser plugins are less relevant
5425 these days, so I thought it was time to look at standalone
5428 <p
>A few days ago I was tired of VLC not being listed as a viable
5429 player when I wanted to play videos from the Norwegian National
5430 Broadcasting Company, and decided to investigate why. The cause is a
5431 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
5432 desktop file
</a
>. In the process I wrote a script to compare the set
5433 of MIME types announced in the desktop file and the browser plugin,
5434 only to discover that there is quite a large difference between the
5435 two for VLC. This discovery made me dig up the script I used to
5436 compare browser plugins, and adjust it to compare desktop files
5437 instead, to try to figure out which multimedia player in Debian
5438 support most file formats.
</p
>
5440 <p
>The result can be seen on the Debian Wiki, as
5441 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
5442 table listing all MIME types supported by one of the packages included
5443 in the table
</a
>, with the package supporting most MIME types being
5444 listed first in the table.
</p
>
5446 </p
>The best multimedia player in Debian? It is totem, followed by
5447 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
5448 kmplayer. Time for the other players to update their announced MIME
5454 <title>The Pyra - handheld computer with Debian preinstalled
</title>
5455 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
5456 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
5457 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
5458 <description>A friend of mine made me aware of
5459 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
5460 handheld computer which will be delivered with Debian preinstalled. I
5461 would love to get one of those for my birthday. :)
</p
>
5463 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
5464 plugs and many others connectors, and include a full keyboard and a
5"
5465 LCD touch screen. The
6000mAh battery is claimed to provide a whole
5466 day of battery life time, but I have not seen any independent tests
5467 confirming this. The vendor is still collecting preorders, and the
5468 last I heard last night was that
22 more orders were needed before
5469 production started.
</p
>
5471 <p
>As far as I know, this is the first handheld preinstalled with
5472 Debian. Please let me know if you know of any others. Is it the
5473 first computer being sold with Debian preinstalled?
</p
>
5478 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
5479 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
5480 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
5481 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
5482 <description><p
>During this weekends
5483 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
5484 squashing party and developer gathering
</a
>, we decided to do our part
5485 to make sure there are good books about Debian available in Norwegian
5486 Bokmål, and got in touch with the people behind the
5487 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
5488 project
</a
> to get started. If you want to help out, please start
5490 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
5491 hosted weblate project page
</a
>, and get in touch using
5492 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
5493 translators mailing list
</a
>. Please also check out
5494 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
5495 contributors
</a
>.
</p
>
5497 <p
>The book is already available on paper in English, French and
5498 Japanese, and our goal is to get it available on paper in Norwegian
5499 Bokmål too. In addition to the paper edition, there are also EPUB and
5500 Mobi versions available. And there are incomplete translations
5501 available for many more languages.
</p
>
5506 <title>One in two hundred Debian users using ZFS on Linux?
</title>
5507 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
5508 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
5509 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
5510 <description><p
>Just for fun I had a look at the popcon number of ZFS related
5511 packages in Debian, and was quite surprised with what I found. I use
5512 ZFS myself at home, but did not really expect many others to do so.
5513 But I might be wrong.
</p
>
5515 <p
>According to
5516 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
5517 results for spl-linux
</a
>, there are
1019 Debian installations, or
5518 0.53% of the population, with the package installed. As far as I know
5519 the only use of the spl-linux package is as a support library for ZFS
5520 on Linux, so I use it here as proxy for measuring the number of ZFS
5521 installation on Linux in Debian. In the kFreeBSD variant of Debian
5522 the ZFS feature is already available, and there
5523 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
5524 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
5525 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
5527 <p
>But even though the Debian project leader Lucas Nussbaum
5528 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
5529 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
5530 cleared, the package is still not in Debian. The package is again in
5531 the NEW queue. Several uploads have been rejected so far because the
5532 debian/copyright file was incomplete or wrong, but there is no reason
5533 to give up. The current status can be seen on
5534 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
5535 team status page
</a
>, and
5536 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
5537 source code
</a
> is available on Alioth.
</p
>
5539 <p
>As I want ZFS to be included in next version of Debian to make sure
5540 my home server can function in the future using only official Debian
5541 packages, and the current blocker is to get the debian/copyright file
5542 accepted by the FTP masters in Debian, I decided a while back to try
5543 to help out the team. This was the background for my blog post about
5544 <a href=
"https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
5545 updating and checking debian/copyright semi-automatically
</a
>, and I
5546 used the techniques I explored there to try to find any errors in the
5547 copyright file. It is not very easy to check every one of the around
5548 2000 files in the source package, but I hope we this time got it
5549 right. If you want to help out, check out the git source and try to
5550 find missing entries in the debian/copyright file.
</p
>
5555 <title>Full battery stats collector is now available in Debian
</title>
5556 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
5557 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
5558 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
5559 <description><p
>Since this morning, the battery-stats package in Debian include an
5560 extended collector that will collect the complete battery history for
5561 later processing and graphing. The original collector store the
5562 battery level as percentage of last full level, while the new
5563 collector also record battery vendor, model, serial number, design
5564 full level, last full level and current battery level. This make it
5565 possible to predict the lifetime of the battery as well as visualise
5566 the energy flow when the battery is charging or discharging.
</p
>
5568 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
5569 in the version
0.5.1 package in unstable. Get the new battery level graph
5570 and lifetime prediction by running:
5572 <p
><pre
>
5573 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
5574 </pre
></p
>
5576 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
5578 <p
>The flow in/out of the battery can be seen by running (no menu
5579 entry yet):
</p
>
5581 <p
><pre
>
5582 /usr/share/battery-stats/battery-stats-graph-flow
5583 </pre
></p
>
5585 <p
>I
'm not quite happy with the way the data is visualised, at least
5586 when there are few data points. The graphs look a bit better with a
5587 few years of data.
</p
>
5589 <p
>A while back one important feature I use in the battery stats
5590 collector broke in Debian. The scripts in
5591 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
5592 suspect it happened when Jessie started using systemd, but I do not
5593 know. The issue is reported as
5594 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
5595 pm-utils. I managed to work around it by adding an udev rule to call
5596 the collector script every time the power connector is connected and
5597 disconnected. With this fix in place it was finally time to make a
5598 new release of the package, and get it into Debian.
</p
>
5600 <p
>If you are interested in how your laptop battery is doing, please
5602 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
5603 in Debian unstable, or rebuild it on Jessie to get it working on
5604 Debian stable. :) The upstream source is available from
5605 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5606 As always, patches are very welcome.
</p
>
5611 <title>Making battery measurements a little easier in Debian
</title>
5612 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
5613 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
5614 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
5615 <description><p
>Back in September, I blogged about
5616 <a href=
"https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
5617 system I wrote to collect statistics about my laptop battery
</a
>, and
5618 how it showed the decay and death of this battery (now replaced). I
5619 created a simple deb package to handle the collection and graphing,
5620 but did not want to upload it to Debian as there were already
5621 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
5622 package in Debian
</a
> that should do the same thing, and I did not see
5623 a point of uploading a competing package when battery-stats could be
5624 fixed instead. I reported a few bugs about its non-function, and
5625 hoped someone would step in and fix it. But no-one did.
</p
>
5627 <p
>I got tired of waiting a few days ago, and took matters in my own
5628 hands. The end result is that I am now the new upstream developer of
5629 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
5630 battery-stats in Debian, and the package in Debian unstable is finally
5631 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
5632 information provided by the Linux kernel. If you install the
5633 battery-stats package from unstable now, you will be able to get a
5634 graph of the current battery fill level, to get some idea about the
5635 status of the battery. The source package build and work just fine in
5636 Debian testing and stable (and probably oldstable too, but I have not
5637 tested). The default graph you get for that system look like this:
</p
>
5639 <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
>
5641 <p
>My plans for the future is to merge my old scripts into the
5642 battery-stats package, as my old scripts collected a lot more details
5643 about the battery. The scripts are merged into the upstream
5644 battery-stats git repository already, but I am not convinced they work
5645 yet, as I changed a lot of paths along the way. Will have to test a
5646 bit more before I make a new release.
</p
>
5648 <p
>I will also consider changing the file format slightly, as I
5649 suspect the way I combine several values into one field might make it
5650 impossible to know the type of the value when using it for processing
5651 and graphing.
</p
>
5653 <p
>If you would like I would like to keep an close eye on your laptop
5654 battery, check out the battery-stats package in
5655 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
5657 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
5658 I would love some help to improve the system further.
</p
>
5663 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
5664 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
5665 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
5666 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
5667 <description><p
>Making packages for Debian requires quite a lot of attention to
5668 details. And one of the details is the content of the
5669 debian/copyright file, which should list all relevant licenses used by
5670 the code in the package in question, preferably in
5671 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
5672 readable DEP5 format
</a
>.
</p
>
5674 <p
>For large packages with lots of contributors it is hard to write
5675 and update this file manually, and if you get some detail wrong, the
5676 package is normally rejected by the ftpmasters. So getting it right
5677 the first time around get the package into Debian faster, and save
5678 both you and the ftpmasters some work.. Today, while trying to figure
5679 out what was wrong with
5680 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
5681 zfsonlinux copyright file
</a
>, I decided to spend some time on
5682 figuring out the options for doing this job automatically, or at least
5683 semi-automatically.
</p
>
5685 <p
>Lucikly, there are at least two tools available for generating the
5686 file based on the code in the source package,
5687 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
5688 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
5689 not sure which one of them came first, but both seem to be able to
5690 create a sensible draft file. As far as I can tell, none of them can
5691 be trusted to get the result just right, so the content need to be
5692 polished a bit before the file is OK to upload. I found the debmake
5694 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
5695 blog posts from
2014</a
>.
5697 <p
>To generate using debmake, use the -cc option:
5699 <p
><pre
>
5700 debmake -cc
> debian/copyright
5701 </pre
></p
>
5703 <p
>Note there are some problems with python and non-ASCII names, so
5704 this might not be the best option.
</p
>
5706 <p
>The cme option is based on a config parsing library, and I found
5708 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
5709 blog post from
2015</a
>. To generate using cme, use the
'update
5710 dpkg-copyright
' option:
5712 <p
><pre
>
5713 cme update dpkg-copyright
5714 </pre
></p
>
5716 <p
>This will create or update debian/copyright. The cme tool seem to
5717 handle UTF-
8 names better than debmake.
</p
>
5719 <p
>When the copyright file is created, I would also like some help to
5720 check if the file is correct. For this I found two good options,
5721 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
5722 to focus on license types and file matching, and is able to detect
5723 ineffective blocks in the copyright file. The latter reports missing
5724 copyright holders and years, but was confused by inconsistent license
5725 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
5726 fix all issues reported by them before uploading. But I do not know
5727 if the tools and the ftpmasters agree on what is important to fix in a
5728 copyright file, so the package might still be rejected.
</p
>
5730 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
5731 will read through the source and try to find all copyright statements.
5732 It is not comparing the result to the content of debian/copyright, but
5733 can be useful when verifying the content of the copyright file.
</p
>
5735 <p
>Are you aware of better tools in Debian to create and update
5736 debian/copyright file. Please let me know, or blog about it on
5737 planet.debian.org.
</p
>
5739 <p
>As usual, if you use Bitcoin and want to show your support of my
5740 activities, please send Bitcoin donations to my address
5741 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5743 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
5744 on how to use licensecheck and cdbs to create a draft copyright file
5746 <p
><pre
>
5747 licensecheck --copyright -r `find * -type f` | \
5748 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
5749 </pre
></p
>
5751 <p
>He mentioned that he normally check the generated file into the
5752 version control system to make it easier to discover license and
5753 copyright changes in the upstream source. I will try to do the same
5754 with my packages in the future.
</p
>
5756 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
5757 against using -quiet for new users, so I removed it from the proposed
5758 command line.
</p
>
5763 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
5764 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
5765 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
5766 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
5767 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
5768 is taking shape in Debian, and one provided feature is a very
5769 convenient way to tell you which package to install to make a given
5770 firmware file available when the kernel is looking for it. This can
5771 be done using apt-file too, but that is for someone else to blog
5774 <p
>Here is a small recipe to find the package with a given firmware
5775 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
5776 picked from the set of firmware announced using appstream in Debian
5777 unstable. In general you would be looking for the firmware requested
5778 by the kernel during kernel module loading. To find the package
5779 providing the example file, do like this:
</p
>
5781 <blockquote
><pre
>
5782 % apt install appstream
5786 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
5787 awk
'/Package:/ {print $
2}
'
5790 </pre
></blockquote
>
5792 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
5793 appstream wiki
</a
> page to learn how to embed the package metadata in
5794 a way appstream can use.
</p
>
5796 <p
>This same approach can be used to find any package supporting a
5797 given MIME type. This is very useful when you get a file you do not
5798 know how to handle. First find the mime type using
<tt
>file
5799 --mime-type
</tt
>, and next look up the package providing support for
5800 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
5801 and you can find all packages handling this type like this:
</p
>
5803 <blockquote
><pre
>
5804 % apt install appstream
5808 % appstreamcli what-provides mimetype image/svg+xml | \
5809 awk
'/Package:/ {print $
2}
'
5831 </pre
></blockquote
>
5833 <p
>I believe the MIME types are fetched from the desktop file for
5834 packages providing appstream metadata.
</p
>
5839 <title>Creepy, visualise geotagged social media information - nice free software
</title>
5840 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
5841 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
5842 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
5843 <description><p
>Most people seem not to realise that every time they walk around
5844 with the computerised radio beacon known as a mobile phone their
5845 position is tracked by the phone company and often stored for a long
5846 time (like every time a SMS is received or sent). And if their
5847 computerised radio beacon is capable of running programs (often called
5848 mobile apps) downloaded from the Internet, these programs are often
5849 also capable of tracking their location (if the app requested access
5850 during installation). And when these programs send out information to
5851 central collection points, the location is often included, unless
5852 extra care is taken to not send the location. The provided
5853 information is used by several entities, for good and bad (what is
5854 good and bad, depend on your point of view). What is certain, is that
5855 the private sphere and the right to free movement is challenged and
5856 perhaps even eradicated for those announcing their location this way,
5857 when they share their whereabouts with private and public
5860 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
5862 <p
>The phone company logs provide a register of locations to check out
5863 when one want to figure out what the tracked person was doing. It is
5864 unavailable for most of us, but provided to selected government
5865 officials, company staff, those illegally buying information from
5866 unfaithful servants and crackers stealing the information. But the
5867 public information can be collected and analysed, and a free software
5868 tool to do so is called
5869 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
5870 discovered it when I read
5871 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
5872 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
5873 November
2014, and decided to check if it was available in Debian.
5874 The python program was in Debian, but
5875 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
5876 Debian
</a
> was completely broken and practically unmaintained. I
5877 uploaded a new version which did not work quite right, but did not
5878 have time to fix it then. This Christmas I decided to finally try to
5879 get Creepy operational in Debian. Now a fixed version is available in
5880 Debian unstable and testing, and almost all Debian specific patches
5882 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
5884 <p
>The Creepy program visualises geolocation information fetched from
5885 Twitter, Instagram, Flickr and Google+, and allow one to get a
5886 complete picture of every social media message posted recently in a
5887 given area, or track the movement of a given individual across all
5888 these services. Earlier it was possible to use the search API of at
5889 least some of these services without identifying oneself, but these
5890 days it is impossible. This mean that to use Creepy, you need to
5891 configure it to log in as yourself on these services, and provide
5892 information to them about your search interests. This should be taken
5893 into account when using Creepy, as it will also share information
5894 about yourself with the services.
</p
>
5896 <p
>The picture above show the twitter messages sent from (or at least
5897 geotagged with a position from) the city centre of Oslo, the capital
5898 of Norway. One useful way to use Creepy is to first look at
5899 information tagged with an area of interest, and next look at all the
5900 information provided by one or more individuals who was in the area.
5901 I tested it by checking out which celebrity provide their location in
5902 twitter messages by checkout out who sent twitter messages near a
5903 Norwegian TV station, and next could track their position over time,
5904 making it possible to locate their home and work place, among other
5905 things. A similar technique have been
5906 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
5907 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
5908 tool to discover lying governments, and a useful tool to help people
5909 understand the value of the private information they provide to the
5912 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
5913 it depend on several python modules currently missing in Jessie (at
5914 least python-instagram, python-flickrapi and
5915 python-requests-toolbelt).
</p
>
5917 <p
>(I have uploaded
5918 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
5919 screenshots.debian.net
</a
> and licensed it under the same terms as the
5920 Creepy program in Debian.)
</p
>
5925 <title>Always download Debian packages using Tor - the simple recipe
</title>
5926 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
5927 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
5928 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
5929 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
5930 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
5931 that those listening on the Internet lines would have good reason to
5932 believe a computer have a given security hole
</a
> if it download a
5933 security fix from a Debian mirror. This is a good reason to always
5934 use encrypted connections to the Debian mirror, to make sure those
5935 listening do not know which IP address to attack. In August, Richard
5936 Hartmann observed that encryption was not enough, when it was possible
5937 to interfere download size to security patches or the fact that
5938 download took place shortly after a security fix was released, and
5939 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
5940 to always use Tor to download packages from the Debian mirror
</a
>. He
5941 was not the first to propose this, as the
5942 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
5943 package by Tim Retout already existed to make it easy to convince apt
5944 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
5945 aware of that package when I read the blog post from Richard.
</p
>
5947 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
5948 sysadmins, and he set up a Tor hidden service on one of the central
5949 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
5950 it possible to download packages directly between two tor nodes,
5951 making sure the network traffic always were encrypted.
</p
>
5953 <p
>Here is a short recipe for enabling this on your machine, by
5954 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
5955 urls with tor+http and tor+https, and using the hidden service instead
5956 of the official Debian mirror site. I recommend installing
5957 <tt
>etckeeper
</tt
> before you start to have a history of the changes
5958 done in /etc/.
</p
>
5960 <blockquote
><pre
>
5961 apt install apt-transport-tor
5962 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
5963 sed -i
's% http% tor+http%
' /etc/apt/sources.list
5964 </pre
></blockquote
>
5966 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
5967 the sed commands for these too. The sed command is assuming your are
5968 using the ftp.debian.org Debian mirror. Adjust the command (or just
5969 edit the file manually) to match your mirror.
</p
>
5971 <p
>This work in Debian Jessie and later. Note that tools like
5972 <tt
>apt-file
</tt
> only recently started using the apt transport
5973 system, and do not work with these tor+http URLs. For
5974 <tt
>apt-file
</tt
> you need the version currently in experimental,
5975 which need a recent apt version currently only in unstable. So if you
5976 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
5978 <p
>Another advantage from this change is that your machine will start
5979 using Tor regularly and at fairly random intervals (every time you
5980 update the package lists or upgrade or install a new package), thus
5981 masking other Tor traffic done from the same machine. Using Tor will
5982 become normal for the machine in question.
</p
>
5984 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
5985 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
5986 enabled. It would be great if it was the default on any Debian
5992 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
5993 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
5994 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
5995 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
5996 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
5997 call the car license plate numbers in those days. I would write the
5998 numbers down in my little book and compare notes with the other kids
5999 to see how many region codes we had seen and if we had seen some
6000 exotic or special region codes and numbers. It was a fun game to pass
6001 time, as we kids have plenty of it.
</p
>
6003 <p
>A few days I came across
6004 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
6005 project
</a
>, a free software project to automatically discover and
6006 report license plates in images and video streams, and provide the
6007 "car numbers
" in a machine readable format. I
've been looking for
6008 such system for a while now, because I believe it is a bad idea that the
6009 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
6010 number plate recognition
</a
> tool only is available in the hands of
6011 the powerful, and want it to be available also for the powerless to
6012 even the score when it comes to surveillance and sousveillance. I
6013 discovered the developer
6014 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
6015 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
6016 help him get it into shape to get the package uploaded into the Debian
6019 <p
>Today we finally managed to get the package into shape and uploaded
6020 it into Debian, where it currently
6021 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
6022 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
6024 <p
>I guess you are wondering why on earth such tool would be useful
6025 for the common folks, ie those not running a large government
6026 surveillance system? Well, I plan to put it in a computer on my bike
6027 and in my car, tracking the cars nearby and allowing me to be notified
6028 when number plates on my watch list are discovered. Another use case
6029 was suggested by a friend of mine, who wanted to set it up at his home
6030 to open the car port automatically when it discovered the plate on his
6031 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
6032 capable of placing his license plate number of a piece of cardboard to
6033 open his car port, men replied that it was always unlocked anyway. I
6034 guess for such use case it make sense. I am sure there are other use
6035 cases too, for those with imagination and a vision.
</p
>
6037 <p
>If you want to build your own version of the Debian package, check
6038 out the upstream git source and symlink ./distros/debian to ./debian/
6039 before running
"debuild
" to build the source. Or wait a bit until the
6040 package show up in unstable.
</p
>
6045 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
6046 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
6047 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
6048 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
6049 <description><p
>Around three years ago, I created
6050 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
6051 system
</a
> to get a more practical solution in Debian for handing
6052 hardware related packages. A GUI system in the isenkram package will
6053 present a pop-up dialog when some hardware dongle supported by
6054 relevant packages in Debian is inserted into the machine. The same
6055 lookup mechanism to detect packages is available as command line
6056 tools in the isenkram-cli package. In addition to mapping hardware,
6057 it will also map kernel firmware files to packages and make it easy to
6058 install needed firmware packages automatically. The key for this
6059 system to work is a good way to map hardware to packages, in other
6060 words, allow packages to announce what hardware they will work
6063 <p
>I started by providing data files in the isenkram source, and
6064 adding code to download the latest version of these data files at run
6065 time, to ensure every user had the most up to date mapping available.
6066 I also added support for storing the mapping in the Packages file in
6067 the apt repositories, but did not push this approach because while I
6068 was trying to figure out how to best store hardware/package mappings,
6069 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
6070 appstream system
</a
> was announced. I got in touch and suggested to
6071 add the hardware mapping into that data set to be able to use
6072 appstream as a data source, and this was accepted at least for the
6073 Debian version of appstream.
</p
>
6075 <p
>A few days ago using appstream in Debian for this became possible,
6076 and today I uploaded a new version
0.20 of isenkram adding support for
6077 appstream as a data source for mapping hardware to packages. The only
6078 package so far using appstream to announce its hardware support is my
6079 pymissile package. I got help from Matthias Klumpp with figuring out
6080 how do add the required
6081 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
6082 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
6083 this content:
</p
>
6085 <blockquote
><pre
>
6086 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
6087 &lt;component
&gt;
6088 &lt;id
&gt;pymissile
&lt;/id
&gt;
6089 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
6090 &lt;name
&gt;pymissile
&lt;/name
&gt;
6091 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
6092 &lt;description
&gt;
6094 Pymissile provides a curses interface to control an original
6095 Marks and Spencer / Striker USB Missile Launcher, as well as a
6096 motion control script to allow a webcamera to control the
6099 &lt;/description
&gt;
6100 &lt;provides
&gt;
6101 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
6102 &lt;/provides
&gt;
6103 &lt;/component
&gt;
6104 </pre
></blockquote
>
6106 <p
>The key for isenkram is the component/provides/modalias value,
6107 which is a glob style match rule for hardware specific strings
6108 (modalias strings) provided by the Linux kernel. In this case, it
6109 will map to all USB devices with vendor code
1130 and product code
6112 <p
>Note, it is important that the license of all the metadata files
6113 are compatible to have permissions to aggregate them into archive wide
6114 appstream files. Matthias suggested to use MIT or BSD licenses for
6115 these files. A challenge is figuring out a good id for the data, as
6116 it is supposed to be globally unique and shared across distributions
6117 (in other words, best to coordinate with upstream what to use). But
6118 it can be changed later or, so we went with the package name as
6119 upstream for this project is dormant.
</p
>
6121 <p
>To get the metadata file installed in the correct location for the
6122 mirror update scripts to pick it up and include its content the
6123 appstream data source, the file must be installed in the binary
6124 package under /usr/share/appdata/. I did this by adding the following
6125 line to debian/pymissile.install:
</p
>
6127 <blockquote
><pre
>
6128 debian/pymissile.metainfo.xml usr/share/appdata
6129 </pre
></blockquote
>
6131 <p
>With that in place, the command line tool isenkram-lookup will list
6132 all packages useful on the current computer automatically, and the GUI
6133 pop-up handler will propose to install the package not already
6134 installed if a hardware dongle is inserted into the machine in
6137 <p
>Details of the modalias field in appstream is available from the
6138 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
6140 <p
>To locate the modalias values of all hardware present in a machine,
6141 try running this command on the command line:
</p
>
6143 <blockquote
><pre
>
6144 cat $(find /sys/devices/|grep modalias)
6145 </pre
></blockquote
>
6147 <p
>To learn more about the isenkram system, please check out
6148 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">my
6149 blog posts tagged isenkram
</a
>.
</p
>
6154 <title>The GNU General Public License is not magic pixie dust
</title>
6155 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
6156 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
6157 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
6158 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
6159 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
6160 GPL is not magic pixie dust
</a
>" explain the importance of making sure
6161 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
6162 I quote the blog post from Paul in full here with his permission:
<p
>
6166 <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
>
6169 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
6171 The first step is to choose a
6172 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
6175 The next step is, when someone fails to follow that copyleft license,
6176 <b
>it must be enforced
</b
><br/
>
6178 and its a simple fact of our modern society that such type of
6181 is incredibly expensive to do and incredibly difficult to do.
6184 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
6185 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
6186 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
6187 0x57</a
></small
></p
>
6189 <p
>As the Debian Website
6190 <a href=
"https://bugs.debian.org/
794116">used
</a
>
6191 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
6192 imply, public domain and permissively licensed software can lead to
6193 the production of more proprietary software as people discover useful
6194 software, extend it and or incorporate it into their hardware or
6195 software products. Copyleft licenses such as the GNU GPL were created
6196 to close off this avenue to the production of proprietary software but
6197 such licenses are not enough. With the ongoing adoption of Free
6198 Software by individuals and groups, inevitably the community
's
6199 expectations of license compliance are violated, usually out of
6200 ignorance of the way Free Software works, but not always. As Karen
6201 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
6202 Freedom
">FaiF
</a
>
6203 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
6204 copyleft is nothing if no-one is willing and able to stand up in court
6205 to protect it. The reality of today
's world is that legal
6206 representation is expensive, difficult and time consuming. With
6207 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
6208 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
6209 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
6210 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
6211 of the Linux project, Debian and other groups against GPL violations.
6212 In March the SFC supported a
6213 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
6214 by Christoph Hellwig
</a
> against VMware for refusing to
6215 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
6216 with the GPL
</a
> in relation to their use of parts of the Linux
6217 kernel. Since then two of their sponsors pulled corporate funding and
6219 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
6220 or cancelled their talks
</a
>. As a result they have decided to rely
6221 less on corporate funding and more on the broad community of
6222 individuals who support Free Software and copyleft. So the SFC has
6223 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
6224 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
6225 a community of folks who stand up for copyleft and the GPL by
6226 supporting their work on promoting and supporting copyleft and Free
6229 <p
>If you support Free Software,
6230 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
6231 what the SFC do, agree with their
6232 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
6233 principles
</a
>, are happy about their
6234 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
6235 work on a project that is an SFC
6236 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
6237 just want to stand up for copyleft, please join
6238 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
6239 Allan Webber
</a
>,
6240 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
6242 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
6243 Bacon
</a
>, myself and
6244 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
6246 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
6247 next week your donation will be
6248 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
6249 by an anonymous donor. Please also consider asking your employer to
6250 match your donation or become a sponsor of SFC. Don
't forget to
6251 spread the word about your support for SFC via email, your blog and or
6252 social media accounts.
</p
>
6256 <p
>I agree with Paul on this topic and just signed up as a Supporter
6257 of Software Freedom Conservancy myself. Perhaps you should be a
6258 supporter too?
</p
>
6263 <title>PGP key transition statement for key EE4E02F9
</title>
6264 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
6265 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
6266 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
6267 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
6268 set it up properly. I wanted to generate it offline and have it
6269 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
6270 smart card
</a
> for daily use, and learning how to do it and finding
6271 time to sit down with an offline machine almost took forever. But
6272 finally I
've been able to complete the process, and have now moved
6273 from my old GPG key to a new GPG key. See
6274 <a href=
"https://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
6275 full transition statement, signed with both my old and new key
</a
> for
6276 the details. This is my new key:
</p
>
6279 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
6280 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
6281 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
6282 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
6283 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
6284 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
6285 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
6288 <p
>The key can be downloaded from the OpenPGP key servers, signed by
6289 my old key.
</p
>
6291 <p
>If you signed my old key
6292 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
6293 I
'd very much appreciate a signature on my new key, details and
6294 instructions in the transition statement. I m happy to reciprocate if
6295 you have a similarly signed transition statement to present.
</p
>
6300 <title>The life and death of a laptop battery
</title>
6301 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
6302 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
6303 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
6304 <description><p
>When I get a new laptop, the battery life time at the start is OK.
6305 But this do not last. The last few laptops gave me a feeling that
6306 within a year, the life time is just a fraction of what it used to be,
6307 and it slowly become painful to use the laptop without power connected
6308 all the time. Because of this, when I got a new Thinkpad X230 laptop
6309 about two years ago, I decided to monitor its battery state to have
6310 more hard facts when the battery started to fail.
</p
>
6312 <img src=
"https://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
6314 <p
>First I tried to find a sensible Debian package to record the
6315 battery status, assuming that this must be a problem already handled
6316 by someone else. I found
6317 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
6318 which collects statistics from the battery, but it was completely
6319 broken. I sent a few suggestions to the maintainer, but decided to
6320 write my own collector as a shell script while I waited for feedback
6322 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
6323 blog post about the battery development on a MacBook Air
</a
> I also
6325 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
6326 available in Debian.
</p
>
6328 <p
>I started my collector
2013-
07-
15, and it has been collecting
6329 battery stats ever since. Now my
6330 /var/log/hjemmenett-battery-status.log file contain around
115,
000
6331 measurements, from the time the battery was working great until now,
6332 when it is unable to charge above
7% of original capacity. My
6333 collector shell script is quite simple and look like this:
</p
>
6338 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
6340 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
6341 logfile=/var/log/hjemmenett-battery-status.log
6343 files=
"manufacturer model_name technology serial_number \
6344 energy_full energy_full_design energy_now cycle_count status
"
6346 if [ ! -e
"$logfile
" ] ; then
6348 printf
"timestamp,
"
6350 printf
"%s,
" $f
6353 )
> "$logfile
"
6357 # Print complete message in one echo call, to avoid race condition
6358 # when several log processes run in parallel.
6359 msg=$(printf
"%s,
" $(date +%s); \
6360 for f in $files; do \
6361 printf
"%s,
" $(cat $f); \
6363 echo
"$msg
"
6366 cd /sys/class/power_supply
6369 (cd $bat
&& log_battery
>> "$logfile
")
6373 <p
>The script is called when the power management system detect a
6374 change in the power status (power plug in or out), and when going into
6375 and out of hibernation and suspend. In addition, it collect a value
6376 every
10 minutes. This make it possible for me know when the battery
6377 is discharging, charging and how the maximum charge change over time.
6378 The code for the Debian package
6379 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
6380 available on github
</a
>.
</p
>
6382 <p
>The collected log file look like this:
</p
>
6385 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
6386 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
6388 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
6389 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
6392 <p
>I wrote a small script to create a graph of the charge development
6393 over time. This graph depicted above show the slow death of my laptop
6396 <p
>But why is this happening? Why are my laptop batteries always
6397 dying in a year or two, while the batteries of space probes and
6398 satellites keep working year after year. If we are to believe
6399 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
6400 University
</a
>, the cause is me charging the battery whenever I have a
6401 chance, and the fix is to not charge the Lithium-ion batteries to
100%
6402 all the time, but to stay below
90% of full charge most of the time.
6403 I
've been told that the Tesla electric cars
6404 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
6405 the charge of their batteries to
80%
</a
>, with the option to charge to
6406 100% when preparing for a longer trip (not that I would want a car
6407 like Tesla where rights to privacy is abandoned, but that is another
6408 story), which I guess is the option we should have for laptops on
6409 Linux too.
</p
>
6411 <p
>Is there a good and generic way with Linux to tell the battery to
6412 stop charging at
80%, unless requested to charge to
100% once in
6413 preparation for a longer trip? I found
6414 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
6415 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
6416 80%
</a
>, but could not get it to work (kernel module refused to
6419 <p
>I wonder why the battery capacity was reported to be more than
100%
6420 at the start. I also wonder why the
"full capacity
" increases some
6421 times, and if it is possible to repeat the process to get the battery
6422 back to design capacity. And I wonder if the discharge and charge
6423 speed change over time, or if this stay the same. I did not yet try
6424 to write a tool to calculate the derivative values of the battery
6425 level, but suspect some interesting insights might be learned from
6428 <p
>Update
2015-
09-
24: I got a tip to install the packages
6429 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
6430 packages instead of the tp-smapi-dkms package I had tried to use
6431 initially, and use
'tlp setcharge
40 80' to change when charging start
6432 and stop. I
've done so now, but expect my existing battery is toast
6433 and need to be replaced. The proposal is unfortunately Thinkpad
6439 <title>New laptop - some more clues and ideas based on feedback
</title>
6440 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
6441 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
6442 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
6443 <description><p
>Several people contacted me after my previous blog post about my
6444 need for a new laptop, and provided very useful feedback. I wish to
6445 thank every one of these. Several pointed me to the possibility of
6446 fixing my X230, and I am already in the process of getting Lenovo to
6447 do so thanks to the on site, next day support contract covering the
6448 machine. But the battery is almost useless (I expect to replace it
6449 with a non-official battery) and I do not expect the machine to live
6450 for many more years, so it is time to plan its replacement. If I did
6451 not have a support contract, it was suggested to find replacement parts
6452 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
6453 might present a language barrier as I do not understand French.
</p
>
6455 <p
>One tip I got was to use the
6456 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
6457 compare laptop models. It seem to have more models available than
6458 prisjakt.no. Another tip I got from someone I know have similar
6459 keyboard preferences was that the HP EliteBook
840 keyboard is not
6460 very good, and this matches my experience with earlier EliteBook
6461 keyboards I tested. Because of this, I will not consider it any further.
6463 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
6464 newest Thinkpad X model. The keyboard reintroduces mouse buttons
6465 (which is missing from the X240), and is working fairly well with
6466 Debian Sid/Unstable according to
6467 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
6468 got on the keyboard quality are not consistent. Some say the keyboard
6469 is good, others say it is ok, while others say it is not very good.
6470 Those with experience from X41 and and X60 agree that the X250
6471 keyboard is not as good as those trusty old laptops, and suggest I
6472 keep and fix my X230 instead of upgrading, or get a used X230 to
6473 replace it. I
'm also told that the X250 lack leds for caps lock, disk
6474 activity and battery status, which is very convenient on my X230. I
'm
6475 also told that the CPU fan is running very often, making it a bit
6476 noisy. In any case, the X250 do not work out of the box with Debian
6477 Stable/Jessie, one of my requirements.
</p
>
6479 <p
>I have also gotten a few vendor proposals, one was
6480 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
6481 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
6482 The latter look very attractive to me.
</p
>
6484 <p
>Again, thank you all for the very useful feedback. It help a lot
6485 as I keep looking for a replacement.
</p
>
6487 <p
>Update
2015-
07-
06: I was recommended to check out the
6488 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
6490 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
6491 thinkpad X models
</a
>, and provide one year warranty.
</p
>
6496 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
6497 <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>
6498 <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>
6499 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
6500 <description><p
>My primary work horse laptop is failing, and will need a
6501 replacement soon. The left
5 cm of the screen on my Thinkpad X230
6502 started flickering yesterday, and I suspect the cause is a broken
6503 cable, as changing the angle of the screen some times get rid of the
6504 flickering.
</p
>
6506 <p
>My requirements have not really changed since I bought it, and is
6508 <a href=
"https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
6509 described them in
2013</a
>. The last time I bought a laptop, I had
6511 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
6512 where I could select at least a few of the requirements (mouse pin,
6513 wifi, weight) and go through the rest manually. Three button mouse
6514 and a good keyboard is not available as an option, and all the three
6515 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
6516 G2) lack three mouse buttons). It is also unclear to me how good the
6517 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
6518 the keyboard, even if the quality and robustness in the X series have
6519 deteriorated since X41.
</p
>
6521 <p
>I wonder how I can find a sensible laptop when none of the options
6522 seem sensible to me? Are there better services around to search the
6523 set of available laptops for features? Please send me an email if you
6524 have suggestions.
</p
>
6526 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
6527 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
6528 of endorsed hardware
</a
>, which is useful background information.
</p
>
6533 <title>How to stay with sysvinit in Debian Jessie
</title>
6534 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
6535 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
6536 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
6537 <description><p
>By now, it is well known that Debian Jessie will not be using
6538 sysvinit as its boot system by default. But how can one keep using
6539 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
6541 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
6542 Schubert
</a
> and
6543 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
6546 <p
>If you already are using Wheezy and want to upgrade to Jessie and
6547 keep sysvinit as your boot system, create a file
6548 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
6549 you upgrade:
</p
>
6551 <p
><blockquote
><pre
>
6552 Package: systemd-sysv
6553 Pin: release o=Debian
6555 </pre
></blockquote
><p
>
6557 <p
>This file content will tell apt and aptitude to not consider
6558 installing systemd-sysv as part of any installation and upgrade
6559 solution when resolving dependencies, and thus tell it to avoid
6560 systemd as a default boot system. The end result should be that the
6561 upgraded system keep using sysvinit.
</p
>
6563 <p
>If you are installing Jessie for the first time, there is no way to
6564 get sysvinit installed by default (debootstrap used by
6565 debian-installer have no option for this), but one can tell the
6566 installer to switch to sysvinit before the first boot. Either by
6567 using a kernel argument to the installer, or by adding a line to the
6568 preseed file used. First, the kernel command line argument:
6570 <p
><blockquote
><pre
>
6571 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
6572 </pre
></blockquote
><p
>
6574 <p
>Next, the line to use in a preseed file:
</p
>
6576 <p
><blockquote
><pre
>
6577 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
6578 </pre
></blockquote
><p
>
6580 <p
>One can of course also do this after the first boot by installing
6581 the sysvinit-core package.
</p
>
6583 <p
>I recommend only using sysvinit if you really need it, as the
6584 sysvinit boot sequence in Debian have several hardware specific bugs
6585 on Linux caused by the fact that it is unpredictable when hardware
6586 devices show up during boot. But on the other hand, the new default
6587 boot system still have a few rough edges I hope will be fixed before
6588 Jessie is released.
</p
>
6590 <p
>Update
2014-
11-
26: Inspired by
6591 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
6592 blog post by Torsten Glaser
</a
>, added --purge to the preseed
6598 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
6599 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
6600 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
6601 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
6602 <description><p
>The right to communicate with your friends and family in private,
6603 without anyone snooping, is a right every citicen have in a liberal
6604 democracy. But this right is under serious attack these days.
</p
>
6606 <p
>A while back it occurred to me that one way to make the dragnet
6607 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
6608 the whisleblower Snowden) more expensive for Internet email,
6609 is to deliver all email using SMTP via Tor. Such SMTP option would be
6610 a nice addition to the FreedomBox project if we could send email
6611 between FreedomBox machines without leaking metadata about the emails
6612 to the people peeking on the wire. I
6613 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
6614 this on the FreedomBox project mailing list in October
</a
> and got a
6615 lot of useful feedback and suggestions. It also became obvious to me
6616 that this was not a novel idea, as the same idea was tested and
6617 documented by Johannes Berg as early as
2006, and both
6618 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
6619 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
6620 propose a similar method / protocol to pass emails between users.
</p
>
6622 <p
>To implement such system one need to set up a Tor hidden service
6623 providing the SMTP protocol on port
25, and use email addresses
6624 looking like username@hidden-service-name.onion. With such addresses
6625 the connections to port
25 on hidden-service-name.onion using Tor will
6626 go to the correct SMTP server. To do this, one need to configure the
6627 Tor daemon to provide the hidden service and the mail server to accept
6628 emails for this .onion domain. To learn more about Exim configuration
6629 in Debian and test the design provided by Johannes Berg in his FAQ, I
6630 set out yesterday to create a Debian package for making it trivial to
6631 set up such SMTP over Tor service based on Debian. Getting it to work
6632 were fairly easy, and
6633 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
6634 source code for the Debian package
</a
> is available from github. I
6635 plan to move it into Debian if further testing prove this to be a
6636 useful approach.
</p
>
6638 <p
>If you want to test this, set up a blank Debian machine without any
6639 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
6640 get rid of exim4). Install tor, clone the git repository mentioned
6641 above, build the deb and install it on the machine. Next, run
6642 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
6643 the instructions to get the service up and running. Restart tor and
6644 exim when it is done, and test mail delivery using swaks like
6647 <p
><blockquote
><pre
>
6648 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
6649 --to fbx@dutlqrrmjhtfa3vp.onion
6650 </pre
></blockquote
></p
>
6652 <p
>This will test the SMTP delivery using tor. Replace the email
6653 address with your own address to test your server. :)
</p
>
6655 <p
>The setup procedure is still to complex, and I hope it can be made
6656 easier and more automatic. Especially the tor setup need more work.
6657 Also, the package include a tor-smtp tool written in C, but its task
6658 should probably be rewritten in some script language to make the deb
6659 architecture independent. It would probably also make the code easier
6660 to review. The tor-smtp tool currently need to listen on a socket for
6661 exim to talk to it and is started using xinetd. It would be better if
6662 no daemon and no socket is needed. I suspect it is possible to get
6663 exim to run a command line tool for delivery instead of talking to a
6664 socket, and hope to figure out how in a future version of this
6667 <p
>Until I wipe my test machine, I can be reached using the
6668 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
6669 SMTorP. :)
</p
>
6674 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
6675 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
6676 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
6677 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
6678 <description><p
>If you ever had to moderate a mailman list, like the ones on
6679 alioth.debian.org, you know the web interface is fairly slow to
6680 operate. First you visit one web page, enter the moderation password
6681 and get a new page shown with a list of all the messages to moderate
6682 and various options for each email address. This take a while for
6683 every list you moderate, and you need to do it regularly to do a good
6684 job as a list moderator. But there is a quick alternative,
6685 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
6686 listadmin program
</a
>. It allow you to check lists for new messages
6687 to moderate in a fraction of a second. Here is a test run on two
6688 lists I recently took over:
</p
>
6690 <p
><blockquote
><pre
>
6691 % time listadmin xiph
6692 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
6693 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
6699 </pre
></blockquote
></p
>
6701 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
6702 there are no message in the moderation queue. Every morning I
6703 currently moderate
68 mailman lists, and it normally take around two
6704 minutes. When I took over the two pkg-xiph lists above a few days
6705 ago, there were
400 emails waiting in the moderator queue. It took me
6706 less than
15 minutes to process them all using the listadmin
6709 <p
>If you install
6710 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
6711 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
6712 with content like this, the moderation task is a breeze:
</p
>
6714 <p
><blockquote
><pre
>
6715 username username@example.org
6718 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
6721 adminurl https://{domain}/mailman/admindb/{list}
6722 mailman-list@lists.example.com
6725 other-list@otherserver.example.org
6726 </pre
></blockquote
></p
>
6728 <p
>There are other options to set as well. Check the manual page to
6729 learn the details.
</p
>
6731 <p
>If you are forced to moderate lists on a mailman installation where
6732 the SSL certificate is self signed or not properly signed by a
6733 generally accepted signing authority, you can set a environment
6734 variable when calling listadmin to disable SSL verification:
</p
>
6736 <p
><blockquote
><pre
>
6737 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
6738 </pre
></blockquote
></p
>
6740 <p
>If you want to moderate a subset of the lists you take care of, you
6741 can provide an argument to the listadmin script like I do in the
6742 initial screen dump (the xiph argument). Using an argument, only
6743 lists matching the argument string will be processed. This make it
6744 quick to accept messages if you notice the moderation request in your
6747 <p
>Without the listadmin program, I would never be the moderator of
68
6748 mailing lists, as I simply do not have time to spend on that if the
6749 process was any slower. The listadmin program have saved me hours of
6750 time I could spend elsewhere over the years. It truly is nice free
6753 <p
>As usual, if you use Bitcoin and want to show your support of my
6754 activities, please send Bitcoin donations to my address
6755 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6757 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
6758 configuration example. Also, I
've been told that the
6759 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
6765 <title>Debian Jessie, PXE and automatic firmware installation
</title>
6766 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
6767 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
6768 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
6769 <description><p
>When PXE installing laptops with Debian, I often run into the
6770 problem that the WiFi card require some firmware to work properly.
6771 And it has been a pain to fix this using preseeding in Debian.
6772 Normally something more is needed. But thanks to
6773 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
6774 package
</a
> and its recent tasksel extension, it has now become easy
6775 to do this using simple preseeding.
</p
>
6777 <p
>The isenkram-cli package provide tasksel tasks which will install
6778 firmware for the hardware found in the machine (actually, requested by
6779 the kernel modules for the hardware). (It can also install user space
6780 programs supporting the hardware detected, but that is not the focus
6781 of this story.)
</p
>
6783 <p
>To get this working in the default installation, two preeseding
6784 values are needed. First, the isenkram-cli package must be installed
6785 into the target chroot (aka the hard drive) before tasksel is executed
6786 in the pkgsel step of the debian-installer system. This is done by
6787 preseeding the base-installer/includes debconf value to include the
6788 isenkram-cli package. The package name is next passed to debootstrap
6789 for installation. With the isenkram-cli package in place, tasksel
6790 will automatically use the isenkram tasks to detect hardware specific
6791 packages for the machine being installed and install them, because
6792 isenkram-cli contain tasksel tasks.
</p
>
6794 <p
>Second, one need to enable the non-free APT repository, because
6795 most firmware unfortunately is non-free. This is done by preseeding
6796 the apt-mirror-setup step. This is unfortunate, but for a lot of
6797 hardware it is the only option in Debian.
</p
>
6799 <p
>The end result is two lines needed in your preseeding file to get
6800 firmware installed automatically by the installer:
</p
>
6802 <p
><blockquote
><pre
>
6803 base-installer base-installer/includes string isenkram-cli
6804 apt-mirror-setup apt-setup/non-free boolean true
6805 </pre
></blockquote
></p
>
6807 <p
>The current version of isenkram-cli in testing/jessie will install
6808 both firmware and user space packages when using this method. It also
6809 do not work well, so use version
0.15 or later. Installing both
6810 firmware and user space packages might give you a bit more than you
6811 want, so I decided to split the tasksel task in two, one for firmware
6812 and one for user space programs. The firmware task is enabled by
6813 default, while the one for user space programs is not. This split is
6814 implemented in the package currently in unstable.
</p
>
6816 <p
>If you decide to give this a go, please let me know (via email) how
6817 this recipe work for you. :)
</p
>
6819 <p
>So, I bet you are wondering, how can this work. First and
6820 foremost, it work because tasksel is modular, and driven by whatever
6821 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
6822 isenkram-cli package place two files for tasksel to find. First there
6823 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
6825 <p
><blockquote
><pre
>
6826 Task: isenkram-packages
6828 Description: Hardware specific packages (autodetected by isenkram)
6829 Based on the detected hardware various hardware specific packages are
6831 Test-new-install: show show
6833 Packages: for-current-hardware
6835 Task: isenkram-firmware
6837 Description: Hardware specific firmware packages (autodetected by isenkram)
6838 Based on the detected hardware various hardware specific firmware
6839 packages are proposed.
6840 Test-new-install: mark show
6842 Packages: for-current-hardware-firmware
6843 </pre
></blockquote
></p
>
6845 <p
>The key parts are Test-new-install which indicate how the task
6846 should be handled and the Packages line referencing to a script in
6847 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
6848 list of packages to install. The for-current-hardware-firmware script
6849 look like this to list relevant firmware for the machine:
6851 <p
><blockquote
><pre
>
6854 PATH=/usr/sbin:$PATH
6856 isenkram-autoinstall-firmware -l
6857 </pre
></blockquote
></p
>
6859 <p
>With those two pieces in place, the firmware is installed by
6860 tasksel during the normal d-i run. :)
</p
>
6862 <p
>If you want to test what tasksel will install when isenkram-cli is
6863 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
6864 --new-install
</tt
> to get the list of packages that tasksel would
6867 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
6868 pilots in testing this feature, as isenkram is used there now to
6869 install firmware, replacing the earlier scripts.
</p
>
6874 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
6875 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
6876 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
6877 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
6878 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
6879 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
6880 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
6881 on a screen normally showing the bread types and prizes:
</p
>
6883 <p align=
"center
"><img width=
"70%
" src=
"https://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
6885 <p
>If it had booted as it was supposed to, I would never had known
6886 about this hidden Linux installation. It is interesting what
6887 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
6892 <title>New lsdvd release version
0.17 is ready
</title>
6893 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
6894 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
6895 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
6896 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
6897 got a new set of developers a few weeks ago, after the original
6898 developer decided to step down and pass the project to fresh blood.
6899 This project is now maintained by Petter Reinholdtsen and Steve
6902 <p
>I just wrapped up
6903 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
6904 new lsdvd release
</a
>, available in git or from
6905 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
6906 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
6911 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
6912 <li
>Check for garbage in the program chains, which indicate that a track is
6913 non-existant, to work around additional copy protection
</li
>
6914 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
6915 <li
>Fix pallete display of first entry
</li
>
6916 <li
>Fix include orders
</li
>
6917 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
6918 <li
>Fix the chapter count
</li
>
6919 <li
>Make sure the array size and the array limit used when initialising
6920 the palette size is the same.
</li
>
6921 <li
>Fix array printing.
</li
>
6922 <li
>Correct subsecond calculations.
</li
>
6923 <li
>Add sector information to the output format.
</li
>
6924 <li
>Clean up code to be closer to ANSI C and compile without warnings
6925 with more GCC compiler warnings.
</li
>
6929 <p
>This change bring together patches for lsdvd in use in various
6930 Linux and Unix distributions, as well as patches submitted to the
6931 project the last nine years. Please check it out. :)
</p
>
6936 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
6937 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
6938 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
6939 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
6940 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6941 project
</a
> provide a Linux solution for schools, including a
6942 powerful desktop with education software, a central server providing
6943 web pages, user database, user home directories, central login and PXE
6944 boot of both clients without disk and the installation to install Debian
6945 Edu on machines with disk (and a few other services perhaps to small
6946 to mention here). We in the Debian Edu team are currently working on
6947 the Jessie based version, trying to get everything in shape before the
6948 freeze, to avoid having to maintain our own package repository in the
6950 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
6951 status
</a
> can be seen on the Debian wiki, and there is still heaps of
6952 work left. Some fatal problems block testing, breaking the installer,
6953 but it is possible to work around these to get anyway. Here is a
6954 recipe on how to get the installation limping along.
</p
>
6956 <p
>First, download the test ISO via
6957 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
6958 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
6960 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
6961 The ISO build was broken on Tuesday, so we do not get a new ISO every
6962 12 hours or so, but thankfully the ISO we already got we are able to
6963 install with some tweaking.
</p
>
6965 <p
>When you get to the Debian Edu profile question, go to tty2
6966 (use Alt-Ctrl-F2), run
</p
>
6968 <p
><blockquote
><pre
>
6969 nano /usr/bin/edu-eatmydata-install
6970 </pre
></blockquote
></p
>
6972 <p
>and add
'exit
0' as the second line, disabling the eatmydata
6973 optimization. Return to the installation, select the profile you want
6974 and continue. Without this change, exim4-config will fail to install
6975 due to a known bug in eatmydata.
</p
>
6977 <p
>When you get the grub question at the end, answer /dev/sda (or if
6978 this do not work, figure out what your correct value would be. All my
6979 test machines need /dev/sda, so I have no advice if it do not fit
6980 your need.
</p
>
6982 <p
>If you installed a profile including a graphical desktop, log in as
6983 root after the initial boot from hard drive, and install the
6984 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
6985 or mate. If you want several desktop options, install more than one
6986 metapackage. Once this is done, reboot and you should have a working
6987 graphical login screen. This workaround should no longer be needed
6988 once the education-tasks package version
1.801 enter testing in two
6991 <p
>I believe the ISO build will start working on two days when the new
6992 tasksel package enter testing and Steve McIntyre get a chance to
6993 update the debian-cd git repository. The eatmydata, grub and desktop
6994 issues are already fixed in unstable and testing, and should show up
6995 on the ISO as soon as the ISO build start working again. Well the
6996 eatmydata optimization is really just disabled. The proper fix
6997 require an upload by the eatmydata maintainer applying the patch
6998 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
6999 The rest have proper fixes in unstable.
</p
>
7001 <p
>I hope this get you going with the installation testing, as we are
7002 quickly running out of time trying to get our Jessie based
7003 installation ready before the distribution freeze in a month.
</p
>
7008 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
7009 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
7010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
7011 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
7012 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
7013 to handle my fairly large DVD collection. It is a nice command line
7014 tool to get details about a DVD, like title, tracks, track length,
7015 etc, in XML, Perl or human readable format. But lsdvd have not seen
7016 any new development since
2006 and had a few irritating bugs affecting
7017 its use with some DVDs. Upstream seemed to be dead, and in January I
7018 sent a small probe asking for a version control repository for the
7019 project, without any reply. But I use it regularly and would like to
7020 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
7021 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
7022 the project admin, and after getting a reply from him explaining that
7023 he was no longer interested in the project, I asked if I could take
7024 over. And yesterday, I became project admin.
</p
>
7026 <p
>I
've been in touch with a Gentoo developer and the Debian
7027 maintainer interested in joining forces to maintain the upstream
7028 project, and I hope we can get a new release out fairly quickly,
7029 collecting the patches spread around on the internet into on place.
7030 I
've added the relevant Debian patches to the freshly created git
7031 repository, and expect the Gentoo patches to make it too. If you got
7032 a DVD collection and care about command line tools, check out
7033 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
7034 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
7035 list
</a
>. :)
</p
>
7040 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
7041 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
7042 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
7043 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
7044 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
7045 a lot quicker. When we install more than
2000 packages in
7046 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
7047 tasksel in the installer, unpacking the binary packages take forever.
7048 A part of the slow I/O issue was discussed in
7049 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
7050 much file system sync-ing done by dpkg, which is the package
7051 responsible for unpacking the binary packages. Other parts (like code
7052 executed by postinst scripts) might also sync to disk during
7053 installation. All this sync-ing to disk do not really make sense to
7054 me. If the machine crash half-way through, I start over, I do not try
7055 to salvage the half installed system. So the failure sync-ing is
7056 supposed to protect against, hardware or system crash, is not really
7057 relevant while the installer is running.
</p
>
7059 <p
>A few days ago, I thought of a way to get rid of all the file
7060 system sync()-ing in a fairly non-intrusive way, without the need to
7061 change the code in several packages. The idea is not new, but I have
7062 not heard anyone propose the approach using dpkg-divert before. It
7063 depend on the small and clever package
7064 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
7065 uses LD_PRELOAD to replace the system functions for syncing data to
7066 disk with functions doing nothing, thus allowing programs to live
7067 dangerous while speeding up disk I/O significantly. Instead of
7068 modifying the implementation of dpkg, apt and tasksel (which are the
7069 packages responsible for selecting, fetching and installing packages),
7070 it occurred to me that we could just divert the programs away, replace
7071 them with a simple shell wrapper calling
7072 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
7073 Two days ago I decided to test the idea, and wrapped up a simple
7074 implementation for the Debian Edu udeb.
</p
>
7076 <p
>The effect was stunning. In my first test it reduced the running
7077 time of the pkgsel step (installing tasks) from
64 to less than
44
7078 minutes (
20 minutes shaved off the installation) on an old Dell
7079 Latitude D505 machine. I am not quite sure what the optimised time
7080 would have been, as I messed up the testing a bit, causing the debconf
7081 priority to get low enough for two questions to pop up during
7082 installation. As soon as I saw the questions I moved the installation
7083 along, but do not know how long the question were holding up the
7084 installation. I did some more measurements using Debian Edu Jessie,
7085 and got these results. The time measured is the time stamp in
7086 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
7087 "pkgsel: finishing up
" lines, if you want to do the same measurement
7088 yourself. In Debian Edu, the tasksel dialog do not show up, and the
7089 timing thus do not depend on how quickly the user handle the tasksel
7092 <p
><table
>
7095 <th
>Machine/setup
</th
>
7096 <th
>Original tasksel
</th
>
7097 <th
>Optimised tasksel
</th
>
7098 <th
>Reduction
</th
>
7102 <td
>Latitude D505 Main+LTSP LXDE
</td
>
7103 <td
>64 min (
07:
46-
08:
50)
</td
>
7104 <td
><44 min (
11:
27-
12:
11)
</td
>
7105 <td
>>20 min
18%
</td
>
7109 <td
>Latitude D505 Roaming LXDE
</td
>
7110 <td
>57 min (
08:
48-
09:
45)
</td
>
7111 <td
>34 min (
07:
43-
08:
17)
</td
>
7112 <td
>23 min
40%
</td
>
7116 <td
>Latitude D505 Minimal
</td
>
7117 <td
>22 min (
10:
37-
10:
59)
</td
>
7118 <td
>11 min (
11:
16-
11:
27)
</td
>
7119 <td
>11 min
50%
</td
>
7123 <td
>Thinkpad X200 Minimal
</td
>
7124 <td
>6 min (
08:
19-
08:
25)
</td
>
7125 <td
>4 min (
08:
04-
08:
08)
</td
>
7126 <td
>2 min
33%
</td
>
7130 <td
>Thinkpad X200 Roaming KDE
</td
>
7131 <td
>19 min (
09:
21-
09:
40)
</td
>
7132 <td
>15 min (
10:
25-
10:
40)
</td
>
7133 <td
>4 min
21%
</td
>
7136 </table
></p
>
7138 <p
>The test is done using a netinst ISO on a USB stick, so some of the
7139 time is spent downloading packages. The connection to the Internet
7140 was
100Mbit/s during testing, so downloading should not be a
7141 significant factor in the measurement. Download typically took a few
7142 seconds to a few minutes, depending on the amount of packages being
7143 installed.
</p
>
7145 <p
>The speedup is implemented by using two hooks in
7146 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
7147 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
7148 finish-install.d hook to remove the divert at the end of the
7149 installation. I picked the pre-pkgsel.d hook instead of the
7150 post-base-installer.d hook because I test using an ISO without the
7151 eatmydata package included, and the post-base-installer.d hook in
7152 Debian Edu can only operate on packages included in the ISO. The
7153 negative effect of this is that I am unable to activate this
7154 optimization for the kernel installation step in d-i. If the code is
7155 moved to the post-base-installer.d hook, the speedup would be larger
7156 for the entire installation.
</p
>
7158 <p
>I
've implemented this in the
7159 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
7160 git repository, and plan to provide the optimization as part of the
7161 Debian Edu installation. If you want to test this yourself, you can
7162 create two files in the installer (or in an udeb). One shell script
7163 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
7165 <p
><blockquote
><pre
>
7168 . /usr/share/debconf/confmodule
7170 logger -t my-pkgsel
"info: $*
"
7173 logger -t my-pkgsel
"error: $*
"
7175 override_install() {
7176 apt-install eatmydata || true
7177 if [ -x /target/usr/bin/eatmydata ] ; then
7178 for bin in dpkg apt-get aptitude tasksel ; do
7180 # Test that the file exist and have not been diverted already.
7181 if [ -f /target$file ] ; then
7182 info
"diverting $file using eatmydata
"
7183 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
7184 > /target$file.edu
7185 chmod
755 /target$file.edu
7186 in-target dpkg-divert --package debian-edu-config \
7187 --rename --quiet --add $file
7188 ln -sf ./$bin.edu /target$file
7190 error
"unable to divert $file, as it is missing.
"
7194 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
7199 </pre
></blockquote
></p
>
7201 <p
>To clean up, another shell script should go into
7202 /usr/lib/finish-install.d/ with code like this:
7204 <p
><blockquote
><pre
>
7206 . /usr/share/debconf/confmodule
7208 logger -t my-finish-install
"error: $@
"
7210 remove_install_override() {
7211 for bin in dpkg apt-get aptitude tasksel ; do
7213 if [ -x /target$file.edu ] ; then
7215 in-target dpkg-divert --package debian-edu-config \
7216 --rename --quiet --remove $file
7219 error
"Missing divert for $file.
"
7222 sync # Flush file buffers before continuing
7225 remove_install_override
7226 </pre
></blockquote
></p
>
7228 <p
>In Debian Edu, I placed both code fragments in a separate script
7229 edu-eatmydata-install and call it from the pre-pkgsel.d and
7230 finish-install.d scripts.
</p
>
7232 <p
>By now you might ask if this change should get into the normal
7233 Debian installer too? I suspect it should, but am not sure the
7234 current debian-installer coordinators find it useful enough. It also
7235 depend on the side effects of the change. I
'm not aware of any, but I
7236 guess we will see if the change is safe after some more testing.
7237 Perhaps there is some package in Debian depending on sync() and
7238 fsync() having effect? Perhaps it should go into its own udeb, to
7239 allow those of us wanting to enable it to do so without affecting
7242 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
7243 will break installation of all programs using gnutls because of
7244 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
7245 eatmydata package in Debian will solve it.
</p
>
7247 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
7248 the optimization work again. And I have discovered that the
7249 dpkg-divert trick is not really needed and implemented a slightly
7250 simpler approach as part of the debian-edu-install package. See
7251 tools/edu-eatmydata-install in the source package.
</p
>
7253 <p
>Update
2014-
11-
11: Unfortunately, a new
7254 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
7255 triggering on i386 made it into testing, and broke this installation
7256 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
7257 request
768893</a
> is accepted, it should be working again.
</p
>
7262 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
7263 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
7264 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
7265 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
7266 <description><p
>Yesterday, I had the pleasure of attending a talk with the
7267 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
7268 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
7269 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
7270 learn that there is a large set of publicly available key servers to
7271 use when looking for peoples public key. So far I have used
7272 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
7273 were misbehaving, but those days are ended. The servers I have used
7274 up until yesterday have been slow and some times unavailable. I hope
7275 those problems are gone now.
</p
>
7277 <p
>Behind the round robin DNS entry of the
7278 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
7279 there is a pool of more than
100 keyservers which are checked every
7280 day to ensure they are well connected and up to date. It must be
7281 better than what I have used so far. :)
</p
>
7283 <p
>Yesterdays speaker told me that the service is the default
7284 keyserver provided by the default configuration in GnuPG, but this do
7285 not seem to be used in Debian. Perhaps it should?
</p
>
7287 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
7290 <p
><blockquote
><pre
>
7291 keyserver pool.sks-keyservers.net
7292 </pre
></blockquote
></p
>
7294 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
7295 entries in DNS. Just for fun, I did just that at work, so now every
7296 user of GnuPG at the University of Oslo should find a OpenGPG
7297 keyserver automatically should their need it:
</p
>
7299 <p
><blockquote
><pre
>
7300 % host -t srv _pgpkey-http._tcp.uio.no
7301 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
7303 </pre
></blockquote
></p
>
7305 <p
>Now if only
7306 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
7307 HKP lookup protocol
</a
> supported finding signature paths, I would be
7308 very happy. It can look up a given key or search for a user ID, but I
7309 normally do not want that, but to find a trust path from my key to
7310 another key. Given a user ID or key ID, I would like to find (and
7311 download) the keys representing a signature path from my key to the
7312 key in question, to be able to get a trust path between the two keys.
7313 This is as far as I can tell not possible today. Perhaps something
7314 for a future version of the protocol?
</p
>
7319 <title>From English wiki to translated PDF and epub via Docbook
</title>
7320 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
7321 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
7322 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
7323 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
7324 project
</a
> provide an instruction manual for teachers, system
7325 administrators and other users that contain useful tips for setting up
7326 and maintaining a Debian Edu installation. This text is about how the
7327 text processing of this manual is handled in the project.
</p
>
7329 <p
>One goal of the project is to provide information in the native
7330 language of its users, and for this we need to handle translations.
7331 But we also want to make sure each language contain the same
7332 information, so for this we need a good way to keep the translations
7333 in sync. And we want it to be easy for our users to improve the
7334 documentation, avoiding the need to learn special formats or tools to
7335 contribute, and the obvious way to do this is to make it possible to
7336 edit the documentation using a web browser. We also want it to be
7337 easy for translators to keep the translation up to date, and give them
7338 help in figuring out what need to be translated. Here is the list of
7339 tools and the process we have found trying to reach all these
7342 <p
>We maintain the authoritative source of our manual in the
7343 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
7344 wiki
</a
>, as several wiki pages written in English. It consist of one
7345 front page with references to the different chapters, several pages
7346 for each chapter, and finally one
"collection page
" gluing all the
7347 chapters together into one large web page (aka
7348 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
7349 AllInOne page
</a
>). The AllInOne page is the one used for further
7350 processing and translations. Thanks to the fact that the
7351 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
7352 wiki.debian.org support exporting pages in
7353 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
7354 the list of pages to export using the raw version of the AllInOne
7355 page, loop over each of them to generate a Docbook XML version of the
7356 manual. This process also download images and transform image
7357 references to use the locally downloaded images. The generated
7358 Docbook XML files are slightly broken, so some post-processing is done
7359 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
7360 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
7361 a handfull of images. The XML file can now be used to generate PDF, HTML
7362 and epub versions of the English manual. This is the basic step of
7363 our process, making PDF (using dblatex), HTML (using xsltproc) and
7364 epub (using dbtoepub) version from Docbook XML, and the resulting files
7365 are placed in the debian-edu-doc-en binary package.
</p
>
7367 <p
>But English documentation is not enough for us. We want translated
7368 documentation too, and we want to make it easy for translators to
7369 track the English original. For this we use the
7370 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
7371 which allow us to transform the English Docbook XML file into a
7372 translation file (a .pot file), usable with the normal gettext based
7373 translation tools used by those translating free software. The pot
7374 file is used to create and maintain translation files (several .po
7375 files), which the translations update with the native language
7376 translations of all titles, paragraphs and blocks of text in the
7377 original. The next step is combining the original English Docbook XML
7378 and the translation file (say debian-edu-wheezy-manual.nb.po), to
7379 create a translated Docbook XML file (in this case
7380 debian-edu-wheezy-manual.nb.xml). This translated (or partly
7381 translated, if the translation is not complete) Docbook XML file can
7382 then be used like the original to create a PDF, HTML and epub version
7383 of the documentation.
</p
>
7385 <p
>The translators use different tools to edit the .po files. We
7387 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
7388 while some use emacs and vi, others can use web based editors like
7389 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
7390 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
7391 is where the .po file end up, in our git repository. Updated
7392 translations can either be committed directly to git, or submitted as
7393 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
7394 against the debian-edu-doc package
</a
>.
</p
>
7396 <p
>One challenge is images, which both might need to be translated (if
7397 they show translated user applications), and are needed in different
7398 formats when creating PDF and HTML versions (epub is a HTML version in
7399 this regard). For this we transform the original PNG images to the
7400 needed density and format during build, and have a way to provide
7401 translated images by storing translated versions in
7402 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
7403 package maintainers know more.
</p
>
7405 <p
>If you wonder what the result look like, we provide
7406 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
7407 of the documentation packages on the web
</a
>. See for example the
7408 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
7409 PDF version
</a
> or the
7410 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
7411 HTML version
</a
>. We do not yet build the epub version by default,
7412 but perhaps it will be done in the future.
</p
>
7414 <p
>To learn more, check out
7415 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
7416 debian-edu-doc package
</a
>,
7417 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
7418 manual on the wiki
</a
> and
7419 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
7420 translation instructions
</a
> in the manual.
</p
>
7425 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
7426 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
7427 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
7428 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
7429 <description><p
>It would be nice if it was easier in Debian to get all the hardware
7430 related packages relevant for the computer installed automatically.
7431 So I implemented one, using
7432 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
7433 package
</a
>. To use it, install the tasksel and isenkram packages and
7434 run tasksel as user root. You should be presented with a new option,
7435 "Hardware specific packages (autodetected by isenkram)
". When you
7436 select it, tasksel will install the packages isenkram claim is fit for
7437 the current hardware, hot pluggable or not.
<p
>
7439 <p
>The implementation is in two files, one is the tasksel menu entry
7440 description, and the other is the script used to extract the list of
7441 packages to install. The first part is in
7442 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
7445 <p
><blockquote
><pre
>
7448 Description: Hardware specific packages (autodetected by isenkram)
7449 Based on the detected hardware various hardware specific packages are
7451 Test-new-install: mark show
7453 Packages: for-current-hardware
7454 </pre
></blockquote
></p
>
7456 <p
>The second part is in
7457 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
7460 <p
><blockquote
><pre
>
7465 isenkram-autoinstall-firmware -l
7467 </pre
></blockquote
></p
>
7469 <p
>All in all, a very short and simple implementation making it
7470 trivial to install the hardware dependent package we all may want to
7471 have installed on our machines. I
've not been able to find a way to
7472 get tasksel to tell you exactly which packages it plan to install
7473 before doing the installation. So if you are curious or careful,
7474 check the output from the isenkram-* command line tools first.
</p
>
7476 <p
>The information about which packages are handling which hardware is
7477 fetched either from the isenkram package itself in
7478 /usr/share/isenkram/, from git.debian.org or from the APT package
7479 database (using the Modaliases header). The APT package database
7480 parsing have caused a nasty resource leak in the isenkram daemon (bugs
7481 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
7482 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
7483 the python-apt code (bug
7484 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
7485 workaround I was able to get rid of the file descriptor leak and
7486 reduce the memory leak from ~
30 MiB per hardware detection down to
7487 around
2 MiB per hardware detection. It should make the desktop
7488 daemon a lot more useful. The fix is in version
0.7 uploaded to
7489 unstable today.
</p
>
7491 <p
>I believe the current way of mapping hardware to packages in
7492 Isenkram is is a good draft, but in the future I expect isenkram to
7493 use the AppStream data source for this. A proposal for getting proper
7494 AppStream support into Debian is floating around as
7495 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
7496 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
7497 project
</a
> will take place this summer to improve the situation. I
7498 look forward to seeing the result, and welcome patches for isenkram to
7499 start using the information when it is ready.
</p
>
7501 <p
>If you want your package to map to some specific hardware, either
7502 add a
"Xb-Modaliases
" header to your control file like I did in
7503 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
7504 package
</a
> or submit a bug report with the details to the isenkram
7506 <a href=
"https://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
7507 blog posts tagged isenkram
</a
> for details on the notation. I expect
7508 the information will be migrated to AppStream eventually, but for the
7509 moment I got no better place to store it.
</p
>
7514 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
7515 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
7516 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
7517 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
7518 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
7519 project
</a
> is working on providing the software and hardware to make
7520 it easy for non-technical people to host their data and communication
7521 at home, and being able to communicate with their friends and family
7522 encrypted and away from prying eyes. It is still going strong, and
7523 today a major mile stone was reached.
</p
>
7525 <p
>Today, the last of the packages currently used by the project to
7526 created the system images were accepted into Debian Unstable. It was
7527 the freedombox-setup package, which is used to configure the images
7528 during build and on the first boot. Now all one need to get going is
7529 the build code from the freedom-maker git repository and packages from
7530 Debian. And once the freedombox-setup package enter testing, we can
7531 build everything directly from Debian. :)
</p
>
7533 <p
>Some key packages used by Freedombox are
7534 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
7535 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
7536 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
7537 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
7538 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
7539 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
7540 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
7541 are plans to integrate more packages into the setup. User
7542 documentation is maintained on the Debian wiki. Please
7543 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
7544 the manual
</a
> and help us improve it.
</p
>
7546 <p
>To test for yourself and create boot images with the FreedomBox
7547 setup, run this on a Debian machine using a user with sudo rights to
7548 become root:
</p
>
7550 <p
><pre
>
7551 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7552 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7554 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7556 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7557 </pre
></p
>
7559 <p
>Root access is needed to run debootstrap and mount loopback
7560 devices. See the README in the freedom-maker git repo for more
7561 details on the build. If you do not want all three images, trim the
7562 make line. Note that the virtualbox-image target is not really
7563 virtualbox specific. It create a x86 image usable in kvm, qemu,
7564 vmware and any other x86 virtual machine environment. You might need
7565 the version of vmdebootstrap in Jessie to get the build working, as it
7566 include fixes for a race condition with kpartx.
</p
>
7568 <p
>If you instead want to install using a Debian CD and the preseed
7569 method, boot a Debian Wheezy ISO and use this boot argument to load
7570 the preseed values:
</p
>
7572 <p
><pre
>
7573 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
7574 </pre
></p
>
7576 <p
>I have not tested it myself the last few weeks, so I do not know if
7577 it still work.
</p
>
7579 <p
>If you wonder how to help, one task you could look at is using
7580 systemd as the boot system. It will become the default for Linux in
7581 Jessie, so we need to make sure it is usable on the Freedombox. I did
7582 a simple test a few weeks ago, and noticed dnsmasq failed to start
7583 during boot when using systemd. I suspect there are other problems
7584 too. :) To detect problems, there is a test suite included, which can
7585 be run from the plinth web interface.
</p
>
7587 <p
>Give it a go and let us know how it goes on the mailing list, and help
7588 us get the new release published. :) Please join us on
7589 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
7590 irc.debian.org)
</a
> and
7591 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7592 mailing list
</a
> if you want to help make this vision come true.
</p
>
7597 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
7598 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
7599 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
7600 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
7601 <description><p
>For a while now, I have been looking for a sensible offsite backup
7602 solution for use at home. My requirements are simple, it must be
7603 cheap and locally encrypted (in other words, I keep the encryption
7604 keys, the storage provider do not have access to my private files).
7605 One idea me and my friends had many years ago, before the cloud
7606 storage providers showed up, was to use Google mail as storage,
7607 writing a Linux block device storing blocks as emails in the mail
7608 service provided by Google, and thus get heaps of free space. On top
7609 of this one can add encryption, RAID and volume management to have
7610 lots of (fairly slow, I admit that) cheap and encrypted storage. But
7611 I never found time to implement such system. But the last few weeks I
7612 have looked at a system called
7613 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
7614 mounted network backed file system with the features I need.
</p
>
7616 <p
>S3QL is a fuse file system with a local cache and cloud storage,
7617 handling several different storage providers, any with Amazon S3,
7618 Google Drive or OpenStack API. There are heaps of such storage
7619 providers. S3QL can also use a local directory as storage, which
7620 combined with sshfs allow for file storage on any ssh server. S3QL
7621 include support for encryption, compression, de-duplication, snapshots
7622 and immutable file systems, allowing me to mount the remote storage as
7623 a local mount point, look at and use the files as if they were local,
7624 while the content is stored in the cloud as well. This allow me to
7625 have a backup that should survive fire. The file system can not be
7626 shared between several machines at the same time, as only one can
7627 mount it at the time, but any machine with the encryption key and
7628 access to the storage service can mount it if it is unmounted.
</p
>
7630 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
7631 package is included already. So to get started, run
<tt
>apt-get
7632 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
7633 Greenqloud, after reading their nice recipe on
7634 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
7635 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
7636 in Iceland more than those in USA when it come to keeping my personal
7637 data safe and private, and thus would rather spend money on a company
7638 in Iceland. Another nice recipe is available from the article
7639 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
7640 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
7641 Admin magazine. When the provider is picked, figure out how to get
7642 the API key needed to connect to the storage API. With Greencloud,
7643 the key did not show up until I had added payment details to my
7646 <p
>Armed with the API access details, it is time to create the file
7647 system. First, create a new bucket in the cloud. This bucket is the
7648 file system storage area. I picked a bucket name reflecting the
7649 machine that was going to store data there, but any name will do.
7650 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
7651 the API login and password, and a locally created password. Store it
7652 all in ~root/.s3ql/authinfo2 like this:
7654 <p
><blockquote
><pre
>
7656 storage-url: s3c://s.greenqloud.com:
443/bucket-name
7657 backend-login: API-login
7658 backend-password: API-password
7659 fs-passphrase: local-password
7660 </pre
></blockquote
></p
>
7662 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
7663 but any sensible way to create a fairly random password should do it.
7664 Armed with these details, it is now time to run mkfs, entering the API
7665 details and password to create it:
</p
>
7667 <p
><blockquote
><pre
>
7668 # mkdir -m
700 /var/lib/s3ql-cache
7669 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7670 --ssl s3c://s.greenqloud.com:
443/bucket-name
7671 Enter backend login:
7672 Enter backend password:
7673 Before using S3QL, make sure to read the user
's guide, especially
7674 the
'Important Rules to Avoid Loosing Data
' section.
7675 Enter encryption password:
7676 Confirm encryption password:
7677 Generating random encryption key...
7678 Creating metadata tables...
7688 Compressing and uploading metadata...
7689 Wrote
0.00 MB of compressed metadata.
7690 #
</pre
></blockquote
></p
>
7692 <p
>The next step is mounting the file system to make the storage available.
7694 <p
><blockquote
><pre
>
7695 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7696 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
7697 Using
4 upload threads.
7698 Downloading and decompressing metadata...
7708 Mounting filesystem...
7710 Filesystem Size Used Avail Use% Mounted on
7711 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
7713 </pre
></blockquote
></p
>
7715 <p
>The file system is now ready for use. I use rsync to store my
7716 backups in it, and as the metadata used by rsync is downloaded at
7717 mount time, no network traffic (and storage cost) is triggered by
7718 running rsync. To unmount, one should not use the normal umount
7719 command, as this will not flush the cache to the cloud storage, but
7720 instead running the umount.s3ql command like this:
7722 <p
><blockquote
><pre
>
7725 </pre
></blockquote
></p
>
7727 <p
>There is a fsck command available to check the file system and
7728 correct any problems detected. This can be used if the local server
7729 crashes while the file system is mounted, to reset the
"already
7730 mounted
" flag. This is what it look like when processing a working
7731 file system:
</p
>
7733 <p
><blockquote
><pre
>
7734 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
7735 Using cached metadata.
7736 File system seems clean, checking anyway.
7737 Checking DB integrity...
7738 Creating temporary extra indices...
7739 Checking lost+found...
7740 Checking cached objects...
7741 Checking names (refcounts)...
7742 Checking contents (names)...
7743 Checking contents (inodes)...
7744 Checking contents (parent inodes)...
7745 Checking objects (reference counts)...
7746 Checking objects (backend)...
7747 ..processed
5000 objects so far..
7748 ..processed
10000 objects so far..
7749 ..processed
15000 objects so far..
7750 Checking objects (sizes)...
7751 Checking blocks (referenced objects)...
7752 Checking blocks (refcounts)...
7753 Checking inode-block mapping (blocks)...
7754 Checking inode-block mapping (inodes)...
7755 Checking inodes (refcounts)...
7756 Checking inodes (sizes)...
7757 Checking extended attributes (names)...
7758 Checking extended attributes (inodes)...
7759 Checking symlinks (inodes)...
7760 Checking directory reachability...
7761 Checking unix conventions...
7762 Checking referential integrity...
7763 Dropping temporary indices...
7764 Backing up old metadata...
7774 Compressing and uploading metadata...
7775 Wrote
0.89 MB of compressed metadata.
7777 </pre
></blockquote
></p
>
7779 <p
>Thanks to the cache, working on files that fit in the cache is very
7780 quick, about the same speed as local file access. Uploading large
7781 amount of data is to me limited by the bandwidth out of and into my
7782 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
7783 which is very close to my upload speed, and downloading the same
7784 Debian installation ISO gave me
610 kiB/s, close to my download speed.
7785 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
7786 network, not the file system code. I do not know what a good cache
7787 size would be, but suspect that the cache should e larger than your
7788 working set.
</p
>
7790 <p
>I mentioned that only one machine can mount the file system at the
7791 time. If another machine try, it is told that the file system is
7794 <p
><blockquote
><pre
>
7795 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7796 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
7797 Using
8 upload threads.
7798 Backend reports that fs is still mounted elsewhere, aborting.
7800 </pre
></blockquote
></p
>
7802 <p
>The file content is uploaded when the cache is full, while the
7803 metadata is uploaded once every
24 hour by default. To ensure the
7804 file system content is flushed to the cloud, one can either umount the
7805 file system, or ask S3QL to flush the cache and metadata using
7808 <p
><blockquote
><pre
>
7809 # s3qlctrl upload-meta /s3ql
7810 # s3qlctrl flushcache /s3ql
7812 </pre
></blockquote
></p
>
7814 <p
>If you are curious about how much space your data uses in the
7815 cloud, and how much compression and deduplication cut down on the
7816 storage usage, you can use s3qlstat on the mounted file system to get
7819 <p
><blockquote
><pre
>
7821 Directory entries:
9141
7824 Total data size:
22049.38 MB
7825 After de-duplication:
21955.46 MB (
99.57% of total)
7826 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
7827 Database size:
2.39 MB (uncompressed)
7828 (some values do not take into account not-yet-uploaded dirty blocks in cache)
7830 </pre
></blockquote
></p
>
7832 <p
>I mentioned earlier that there are several possible suppliers of
7833 storage. I did not try to locate them all, but am aware of at least
7834 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
7835 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
7836 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
7837 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
7838 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
7839 accept payment in Bitcoin. Pick one that suit your need. Some of
7840 them provide several GiB of free storage, but the prize models are
7841 quite different and you will have to figure out what suits you
7844 <p
>While researching this blog post, I had a look at research papers
7845 and posters discussing the S3QL file system. There are several, which
7846 told me that the file system is getting a critical check by the
7847 science community and increased my confidence in using it. One nice
7849 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
7850 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
7851 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
7852 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
7853 and Pamela Smith. Please have a look.
</p
>
7855 <p
>Given my problems with different file systems earlier, I decided to
7856 check out the mounted S3QL file system to see if it would be usable as
7857 a home directory (in other word, that it provided POSIX semantics when
7858 it come to locking and umask handling etc). Running
7859 <a href=
"https://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
7860 test code to check file system semantics
</a
>, I was happy to discover that
7861 no error was found. So the file system can be used for home
7862 directories, if one chooses to do so.
</p
>
7864 <p
>If you do not want a locally file system, and want something that
7865 work without the Linux fuse file system, I would like to mention the
7866 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
7867 provide locally encrypted backup using a command line client. It have
7868 a nicer access control system, where one can split out read and write
7869 access, allowing some systems to write to the backup and others to
7870 only read from it.
</p
>
7872 <p
>As usual, if you use Bitcoin and want to show your support of my
7873 activities, please send Bitcoin donations to my address
7874 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7879 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
7880 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
7881 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
7882 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
7883 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
7884 project
</a
> is working on providing the software and hardware for
7885 making it easy for non-technical people to host their data and
7886 communication at home, and being able to communicate with their
7887 friends and family encrypted and away from prying eyes. It has been
7888 going on for a while, and is slowly progressing towards a new test
7889 release (
0.2).
</p
>
7891 <p
>And what day could be better than the Pi day to announce that the
7892 new version will provide
"hard drive
" / SD card / USB stick images for
7893 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
7894 system), and can also be installed using a Debian installer preseed
7895 file. The Debian based Freedombox is now based on Debian Jessie,
7896 where most of the needed packages used are already present. Only one,
7897 the freedombox-setup package, is missing. To try to build your own
7898 boot image to test the current status, fetch the freedom-maker scripts
7900 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
7901 with a user with sudo access to become root:
7904 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7906 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7907 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7909 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7912 <p
>Root access is needed to run debootstrap and mount loopback
7913 devices. See the README for more details on the build. If you do not
7914 want all three images, trim the make line. But note that thanks to
<a
7915 href=
"https://bugs.debian.org/
741407">a race condition in
7916 vmdebootstrap
</a
>, the build might fail without the patch to the
7917 kpartx call.
</p
>
7919 <p
>If you instead want to install using a Debian CD and the preseed
7920 method, boot a Debian Wheezy ISO and use this boot argument to load
7921 the preseed values:
</p
>
7924 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
7927 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
7928 recently introduced bug in apt in Jessie
</a
>, the installer will
7929 currently hang while setting up APT sources. Killing the
7930 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
7931 installation will get the installation going. This affect all
7932 installations in Jessie, and I expect it will be fixed soon.
</p
>
7934 <p
>Give it a go and let us know how it goes on the mailing list, and help
7935 us get the new release published. :) Please join us on
7936 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
7937 irc.debian.org)
</a
> and
7938 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7939 mailing list
</a
> if you want to help make this vision come true.
</p
>
7944 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
7945 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
7946 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
7947 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
7948 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
7949 innetgr tools, because I needed them in
7950 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
7951 ng-utils, and it has served me well. I placed the project under the
7952 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
7953 repository. But many years ago, the CVS repository was dropped (lost,
7954 not migrated to new hardware, not sure), and the project have lacked a
7955 proper home since then.
</p
>
7957 <p
>Last summer, I had a look at the package and made a new release
7958 fixing a irritating crash bug, but was unable to store the changes in
7959 a proper source control system. I applied for a project on
7960 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
7961 to follow up on it. Until today. :)
</p
>
7963 <p
>After many hours of cleaning and migration, the ng-utils project
7964 now have a new home, and a git repository with the highlight of the
7965 history of the project. I published all release tarballs and imported
7966 them into the git repository. As the project is really stable and not
7967 expected to gain new features any time soon, I decided to make a new
7968 release and call it
1.0. Visit the new project home on
7969 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
7970 if you want to check it out. The new version is also uploaded into
7971 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
7976 <title>Testing sysvinit from experimental in Debian Hurd
</title>
7977 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
7978 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
7979 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
7980 <description><p
>A few days ago I decided to try to help the Hurd people to get
7981 their changes into sysvinit, to allow them to use the normal sysvinit
7982 boot system instead of their old one. This follow up on the
7983 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
7984 Google Summer of Code work
</a
> done last summer by Justus Winter to
7985 get Debian on Hurd working more like Debian on Linux. To get started,
7986 I downloaded a prebuilt hard disk image from
7987 <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
>,
7988 and started it using virt-manager.
</p
>
7990 <p
>The first think I had to do after logging in (root without any
7991 password) was to get the network operational. I followed
7992 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
7993 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
7994 commands as root to get the machine to accept a IP address from the
7995 kvm internal DHCP server:
</p
>
7997 <p
><blockquote
><pre
>
7998 settrans -fgap /dev/netdde /hurd/netdde
7999 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
8000 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
8002 </pre
></blockquote
></p
>
8004 <p
>After this, the machine had internet connectivity, and I could
8005 upgrade it and install the sysvinit packages from experimental and
8006 enable it as the default boot system in Hurd.
</p
>
8008 <p
>But before I did that, I set a password on the root user, as ssh is
8009 running on the machine it for ssh login to work a password need to be
8010 set. Also, note that a bug somewhere in openssh on Hurd block
8011 compression from working. Remember to turn that off on the client
8014 <p
>Run these commands as root to upgrade and test the new sysvinit
8017 <p
><blockquote
><pre
>
8018 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
8019 deb http://http.debian.net/debian/ experimental main
8022 apt-get dist-upgrade
8023 apt-get install -t experimental initscripts sysv-rc sysvinit \
8024 sysvinit-core sysvinit-utils
8025 update-alternatives --config runsystem
8026 </pre
></blockquote
></p
>
8028 <p
>To reboot after switching boot system, you have to use
8029 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
8030 yet a sysvinit process able to receive the signals from the normal
8031 'reboot
' command. After switching to sysvinit as the boot system,
8032 upgrading every package and rebooting, the network come up with DHCP
8033 after boot as it should, and the settrans/pkill hack mentioned at the
8034 start is no longer needed. But for some strange reason, there are no
8035 longer any login prompt in the virtual console, so I logged in using
8038 <p
>Note that there are some race conditions in Hurd making the boot
8039 fail some times. No idea what the cause is, but hope the Hurd porters
8040 figure it out. At least Justus said on IRC (#debian-hurd on
8041 irc.debian.org) that they are aware of the problem. A way to reduce
8042 the impact is to upgrade to the Hurd packages built by Justus by
8043 adding this repository to the machine:
</p
>
8045 <p
><blockquote
><pre
>
8046 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
8047 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
8049 </pre
></blockquote
></p
>
8051 <p
>At the moment the prebuilt virtual machine get some packages from
8052 http://ftp.debian-ports.org/debian, because some of the packages in
8053 unstable do not yet include the required patches that are lingering in
8054 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
8056 <p
><blockquote
><pre
>
8057 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
8058 i emacs - GNU Emacs editor (metapackage)
8059 i gdb - GNU Debugger
8060 i hurd-recommended - Miscellaneous translators
8061 i isc-dhcp-client - ISC DHCP client
8062 i isc-dhcp-common - common files used by all the isc-dhcp* packages
8063 i libc-bin - Embedded GNU C Library: Binaries
8064 i libc-dev-bin - Embedded GNU C Library: Development binaries
8065 i libc0.3 - Embedded GNU C Library: Shared libraries
8066 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
8067 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
8068 i multiarch-support - Transitional package to ensure multiarch compatibilit
8069 i A x11-common - X Window System (X.Org) infrastructure
8070 i xorg - X.Org X Window System
8071 i A xserver-xorg - X.Org X server
8072 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
8074 </pre
></blockquote
></p
>
8076 <p
>All in all, testing hurd has been an interesting experience. :)
8077 X.org did not work out of the box and I never took the time to follow
8078 the porters instructions to fix it. This time I was interested in the
8079 command line stuff.
<p
>
8084 <title>New chrpath release
0.16</title>
8085 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
8086 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
8087 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
8088 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
8089 find problems in C, C++ and Java code using static source code
8090 analysis. It can detect a lot of different problems, and is very
8091 useful to find memory and locking bugs in the error handling part of
8092 the source. The company behind it provide
8093 <a href=
"https://scan.coverity.com/
">check of free software projects as
8094 a community service
</a
>, and many hundred free software projects are
8095 already checked. A few days ago I decided to have a closer look at
8096 the Coverity system, and discovered that the
8097 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
8098 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
8099 projects I am involved with was already registered. But these are
8100 fairly big, and I would also like to have a small and easy project to
8101 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
8102 checking of the chrpath project
</a
>. It was
8103 added to the checker and discovered seven potential defects. Six of
8104 these were real, mostly resource
"leak
" when the program detected an
8105 error. Nothing serious, as the resources would be released a fraction
8106 of a second later when the program exited because of the error, but it
8107 is nice to do it right in case the source of the program some time in
8108 the future end up in a library. Having fixed all defects and added
8109 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
8110 mailing list for the chrpath developers
</a
>, I decided it was time to
8111 publish a new release. These are the release notes:
</p
>
8113 <p
>New in
0.16 released
2014-
01-
14:
</p
>
8117 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
8118 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
8119 <li
>Mention new project mailing list in the documentation.
</li
>
8124 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
8125 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
8126 project if something is wrong with the new release. The test suite
8127 did not discover any old errors, so if you find a new one, please also
8128 include a test suite check.
</p
>
8133 <title>New chrpath release
0.15</title>
8134 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
8135 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
8136 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
8137 <description><p
>After many years break from the package and a vain hope that
8138 development would be continued by someone else, I finally pulled my
8139 acts together this morning and wrapped up a new release of chrpath,
8140 the command line tool to modify the rpath and runpath of already
8141 compiled ELF programs. The update was triggered by the persistence of
8142 Isha Vishnoi at IBM, which needed a new config.guess file to get
8143 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
8144 is working on. I checked the
8145 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
8146 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
8147 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
8148 packages for interesting patches (failed to find the source from
8149 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
8150 These are the release notes:
</p
>
8152 <p
>New in
0.15 released
2013-
11-
24:
</p
>
8156 <li
>Updated config.sub and config.guess from the GNU project to work
8157 with newer architectures. Thanks to isha vishnoi for the heads
8160 <li
>Updated README with current URLs.
</li
>
8162 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
8163 Matthias Klose.
</li
>
8165 <li
>Added missing help for -k|--keepgoing option, using patch by
8166 Petr Machata found in Fedora.
</li
>
8168 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
8169 .dynamic is a NULL terminated string. Based on patch found in
8170 Fedora credited Axel Thimm and Christian Krause.
</li
>
8175 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
8176 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
8177 project if something is wrong with the new release. The test suite
8178 did not discover any old errors, so if you find a new one, please also
8179 include a testsuite check.
</p
>
8184 <title>Debian init.d boot script example for rsyslog
</title>
8185 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
8186 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
8187 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
8188 <description><p
>If one of the points of switching to a new init system in Debian is
8189 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
8190 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
8191 init.d scripts at all. Here is an example init.d script, ie a rewrite
8192 of /etc/init.d/rsyslog:
</p
>
8194 <p
><pre
>
8195 #!/lib/init/init-d-script
8198 # Required-Start: $remote_fs $time
8199 # Required-Stop: umountnfs $time
8200 # X-Stop-After: sendsigs
8201 # Default-Start:
2 3 4 5
8202 # Default-Stop:
0 1 6
8203 # Short-Description: enhanced syslogd
8204 # Description: Rsyslog is an enhanced multi-threaded syslogd.
8205 # It is quite compatible to stock sysklogd and can be
8206 # used as a drop-in replacement.
8208 DESC=
"enhanced syslogd
"
8209 DAEMON=/usr/sbin/rsyslogd
8210 </pre
></p
>
8212 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
8213 script was
137 lines, and the above is just
15 lines, most of it meta
8214 info/comments.
</p
>
8216 <p
>How to do this, you ask? Well, one create a new script
8217 /lib/init/init-d-script looking something like this:
8219 <p
><pre
>
8222 # Define LSB log_* functions.
8223 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
8224 # and status_of_proc is working.
8225 . /lib/lsb/init-functions
8228 # Function that starts the daemon/service
8234 #
0 if daemon has been started
8235 #
1 if daemon was already running
8236 #
2 if daemon could not be started
8237 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
8239 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
8242 # Add code here, if necessary, that waits for the process to be ready
8243 # to handle requests from services started subsequently which depend
8244 # on this one. As a last resort, sleep for some time.
8248 # Function that stops the daemon/service
8253 #
0 if daemon has been stopped
8254 #
1 if daemon was already stopped
8255 #
2 if daemon could not be stopped
8256 # other if a failure occurred
8257 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
8258 RETVAL=
"$?
"
8259 [
"$RETVAL
" =
2 ]
&& return
2
8260 # Wait for children to finish too if this is a daemon that forks
8261 # and if the daemon is only ever run from this initscript.
8262 # If the above conditions are not satisfied then add some other code
8263 # that waits for the process to drop all resources that could be
8264 # needed by services started subsequently. A last resort is to
8265 # sleep for some time.
8266 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
8267 [
"$?
" =
2 ]
&& return
2
8268 # Many daemons don
't delete their pidfiles when they exit.
8270 return
"$RETVAL
"
8274 # Function that sends a SIGHUP to the daemon/service
8278 # If the daemon can reload its configuration without
8279 # restarting (for example, when it is sent a SIGHUP),
8280 # then implement that here.
8282 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
8287 scriptbasename=
"$(basename $
1)
"
8288 echo
"SN: $scriptbasename
"
8289 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
8290 script=
"$
1"
8297 NAME=$(basename $DAEMON)
8298 PIDFILE=/var/run/$NAME.pid
8300 # Exit if the package is not installed
8301 #[ -x
"$DAEMON
" ] || exit
0
8303 # Read configuration variable file if it is present
8304 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
8306 # Load the VERBOSE setting and other rcS variables
8309 case
"$
1" in
8311 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
8313 case
"$?
" in
8314 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
8315 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
8319 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
8321 case
"$?
" in
8322 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
8323 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
8327 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
8329 #reload|force-reload)
8331 # If do_reload() is not implemented then leave this commented out
8332 # and leave
'force-reload
' as an alias for
'restart
'.
8334 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
8338 restart|force-reload)
8340 # If the
"reload
" option is implemented then remove the
8341 #
'force-reload
' alias
8343 log_daemon_msg
"Restarting $DESC
" "$NAME
"
8345 case
"$?
" in
8348 case
"$?
" in
8350 1) log_end_msg
1 ;; # Old process is still running
8351 *) log_end_msg
1 ;; # Failed to start
8361 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
8367 </pre
></p
>
8369 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
8370 lot. I did not really polish the approach, so it might not always
8371 work out of the box, but you get the idea. I did not try very hard to
8372 optimize it nor make it more robust either.
</p
>
8374 <p
>A better argument for switching init system in Debian than reducing
8375 the size of init scripts (which is a good thing to do anyway), is to
8376 get boot system that is able to handle the kernel events sensibly and
8377 robustly, and do not depend on the boot to run sequentially. The boot
8378 and the kernel have not behaved sequentially in years.
</p
>
8383 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
8384 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
8385 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
8386 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
8387 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
8388 remote display access is the preferred solution with oVirt and RedHat
8389 Enterprise Virtualization, and I was sad to discover the other day
8390 that the browser plugin needed to use these systems seamlessly was
8391 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
8392 for a package
</a
> was from
2012-
04-
10 with no progress since
8393 2013-
04-
01, so I decided to wrap up a package based on the great work
8394 from Cajus Pollmeier and put it in a collab-maint maintained git
8395 repository to get a package I could use. I would very much like
8396 others to help me maintain the package (or just take over, I do not
8397 mind), but as no-one had volunteered so far, I just uploaded it to
8398 NEW. I hope it will be available in Debian in a few days.
</p
>
8400 <p
>The source is now available from
8401 <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
>
8406 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
8407 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
8408 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
8409 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
8410 <description><p
>The
8411 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
8412 program is a a very nice system to create virtual machine images. It
8413 create a image file, add a partition table, mount it and run
8414 debootstrap in the mounted directory to create a Debian system on a
8415 stick. Yesterday, I decided to try to teach it how to make images for
8416 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
8417 of a plan to simplify the build system for
8418 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
8419 project
</a
>. The FreedomBox project already uses vmdebootstrap for
8420 the virtualbox images, but its current build system made multistrap
8421 based system for Dreamplug images, and it is lacking support for
8422 Raspberry Pi.
</p
>
8424 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
8425 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
8426 code and adjusted it to be able to build armel images on my amd64
8427 Debian laptop. I ended up giving vmdebootstrap five new options,
8428 allowing me to replicate the image creation process I use to make
8429 <a href=
"https://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
8430 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
8431 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
8432 call debootstrap with --foreign and to copy the handler into the
8433 generated chroot before running the second stage. This allow
8434 vmdebootstrap to create armel images on an amd64 host. Next I added
8435 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
8436 fstype
</tt
> to teach it to create a separate /boot/ partition with the
8437 given file system type, allowing me to create an image with a vfat
8438 partition for the /boot/ stuff. I also added a
<tt
>--variant
8439 variant
</tt
> option to allow me to create smaller images without the
8440 Debian base system packages installed. Finally, I added an option
8441 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
8442 as a boot loader. It is not needed on the Raspberry Pi and probably
8443 most other non-x86 architectures. The changes were accepted by the
8444 upstream author of vmdebootstrap yesterday and today, and is now
8446 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
8447 upstream project page
</a
>.
</p
>
8449 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
8450 create a small script (the customize script) to add the non-free
8451 binary blob needed to boot the Raspberry Pi and the APT source
8454 <p
><pre
>
8456 set -e # Exit on first error
8457 rootdir=
"$
1"
8458 cd
"$rootdir
"
8459 cat
&lt;
&lt;EOF
> etc/apt/sources.list
8460 deb http://http.debian.net/debian/ jessie main contrib non-free
8462 # Install non-free binary blob needed to boot Raspberry Pi. This
8463 # install a kernel somewhere too.
8464 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
8465 -O $rootdir/usr/bin/rpi-update
8466 chmod a+x $rootdir/usr/bin/rpi-update
8467 mkdir -p $rootdir/lib/modules
8468 touch $rootdir/boot/start.elf
8469 chroot $rootdir rpi-update
8470 </pre
></p
>
8472 <p
>Next, fetch the latest vmdebootstrap script and call it like this
8473 to build the image:
</p
>
8476 sudo ./vmdebootstrap \
8479 --distribution jessie \
8480 --mirror http://http.debian.net/debian \
8489 --root-password raspberry \
8490 --hostname raspberrypi \
8491 --foreign /usr/bin/qemu-arm-static \
8492 --customize `pwd`/customize \
8494 --package git-core \
8495 --package binutils \
8496 --package ca-certificates \
8499 </pre
></p
>
8501 <p
>The list of packages being installed are the ones needed by
8502 rpi-update to make the image bootable on the Raspberry Pi, with the
8503 exception of netbase, which is needed by debootstrap to find
8504 /etc/hosts with the minbase variant. I really wish there was a way to
8505 set up an Raspberry Pi using only packages in the Debian archive, but
8506 that is not possible as far as I know, because it boots from the GPU
8507 using a non-free binary blob.
</p
>
8509 <p
>The build host need debootstrap, kpartx and qemu-user-static and
8510 probably a few others installed. I have not checked the complete
8511 build dependency list.
</p
>
8513 <p
>The resulting image will not use the hardware floating point unit
8514 on the Raspberry PI, because the armel architecture in Debian is not
8515 optimized for that use. So the images created will be a bit slower
8516 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
8521 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
8522 <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>
8523 <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>
8524 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
8525 <description><p
>The last few days I came across a few good causes that should get
8526 wider attention. I recommend signing and donating to each one of
8529 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
8530 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
8531 Women program which is a Google Summer of Code like initiative to get
8532 more women involved in free software. One debian sponsor has offered
8533 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
8534 earmarked
</a
> for this initiative. I donated a few minutes ago, and
8535 hope you will to. :)
</p
>
8537 <p
>And the Electronic Frontier Foundation just announced plans to
8538 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
8539 documentaries about the excessive spying
</a
> on every Internet user that
8540 take place these days, and their need to fund the work. I
've already
8541 donated. Are you next?
</p
>
8543 <p
>For my Norwegian audience, the organisation Studentenes og
8544 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
8545 statement under the heading
8546 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
8547 Access
</a
> for those of us asking for more focus on open access in the
8548 Norwegian government. So far
499 signatures. I hope you will sign it
8554 <title>Videos about the Freedombox project - for inspiration and learning
</title>
8555 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
8556 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
8557 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
8558 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
8559 project
</a
> have been going on for a while, and have presented the
8560 vision, ideas and solution several places. Here is a little
8561 collection of videos of talks and presentation of the project.
</p
>
8565 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
8566 2,
5 minute marketing film
</a
> (Youtube)
</li
>
8568 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
8569 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
8571 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
8572 Freedom in the Cloud - Software Freedom, Privacy and and Security for
8573 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
8574 (Youtube)
</li
>
8576 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
8577 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
8579 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
8580 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
8582 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
8583 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
8584 York City in
2012</a
> (Youtube)
</li
>
8586 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
8587 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
8588 (Youtube)
</li
>
8590 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
8591 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
8593 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
8594 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
8596 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
8597 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
8598 2013</a
> (Youtube)
</li
>
8602 <p
>A larger list is available from
8603 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
8604 Freedombox Wiki
</a
>.
</p
>
8606 <p
>On other news, I am happy to report that Freedombox based on Debian
8607 Jessie is coming along quite well, and soon both Owncloud and using
8608 Tor should be available for testers of the Freedombox solution. :) In
8609 a few weeks I hope everything needed to test it is included in Debian.
8610 The withsqlite package is already in Debian, and the plinth package is
8611 pending in NEW. The third and vital part of that puzzle is the
8612 metapackage/setup framework, which is still pending an upload. Join
8613 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
8614 (#freedombox on irc.debian.org)
</a
> and
8615 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
8616 mailing list
</a
> if you want to help make this vision come true.
</p
>
8621 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
8622 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
8623 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
8624 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
8625 <description><p
>I was introduced to the
8626 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
8627 in
2010, when Eben Moglen presented his vision about serving the need
8628 of non-technical people to keep their personal information private and
8629 within the legal protection of their own homes. The idea is to give
8630 people back the power over their network and machines, and return
8631 Internet back to its intended peer-to-peer architecture. Instead of
8632 depending on a central service, the Freedombox will give everyone
8633 control over their own basic infrastructure.
</p
>
8635 <p
>I
've intended to join the effort since then, but other tasks have
8636 taken priority. But this summers nasty news about the misuse of trust
8637 and privilege exercised by the
"western
" intelligence gathering
8638 communities increased my eagerness to contribute to a point where I
8639 actually started working on the project a while back.
</p
>
8641 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
8642 Debian initiative
</a
> based on the vision from Eben Moglen, is to
8643 create a simple and cheap Debian based appliance that anyone can hook
8644 up in their home and get access to secure and private services and
8645 communication. The initial deployment platform have been the
8646 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
8647 which is a piece of hardware I do not own. So to be able to test what
8648 the current Freedombox setup look like, I had to come up with a way to install
8649 it on some hardware I do have access to. I have rewritten the
8650 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
8651 image build framework to use .deb packages instead of only copying
8652 setup into the boot images, and thanks to this rewrite I am able to
8653 set up any machine supported by Debian Wheezy as a Freedombox, using
8654 the previously mentioned deb (and a few support debs for packages
8655 missing in Debian).
</p
>
8657 <p
>The current Freedombox setup consist of a set of bootstrapping
8659 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
8660 and a administrative web interface
8661 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
8662 withsqlite), as well as a privacy enhancing proxy based on
8663 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
8664 (freedombox-privoxy). There is also a web/javascript based XMPP
8665 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
8666 trying (unsuccessfully so far) to talk to the XMPP server
8667 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
8668 web interface is pluggable, and the goal is to use it to enable OpenID
8669 services, mesh network connectivity, use of TOR, etc, etc. Not much of
8670 this is really working yet, see
8671 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
8672 project TODO
</a
> for links to GIT repositories. Most of the code is
8673 on github at the moment. The HTTP proxy is operational out of the
8674 box, and the admin web interface can be used to add/remove plinth
8675 users. I
've not been able to do anything else with it so far, but
8676 know there are several branches spread around github and other places
8677 with lots of half baked features.
</p
>
8679 <p
>Anyway, if you want to have a look at the current state, the
8680 following recipes should work to give you a test machine to poke
8683 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
8687 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
8688 <li
>Boot from it, either as CD or USB stick.
</li
>
8689 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
8690 to the Debian installer:
<p
>
8691 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
8693 <li
>Answer the few language/region/password questions and pick disk to
8694 install on.
</li
>
8696 <li
>When the installation is finished and the machine have rebooted a
8697 few times, your Freedombox is ready for testing.
</li
>
8701 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
8705 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
8706 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
8707 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
8709 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
8710 </pre
></li
>
8711 <li
><p
>Run this as root:
</p
>
8713 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
8716 apt-get install freedombox-setup
8717 /usr/lib/freedombox/setup
8718 </pre
></li
>
8719 <li
>Reboot into your freshly created Freedombox.
</li
>
8723 <p
>You can test it on other architectures too, but because the
8724 freedombox-privoxy package is binary, it will only work as intended on
8725 the architectures where I have had time to build the binary and put it
8726 in my APT repository. But do not let this stop you. It is only a
8727 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
8729 <p
>Note that by default Freedombox is a DHCP server on the
8730 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
8731 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
8732 disable
</tt
>" as root.
</p
>
8734 <p
>Please let me know if this works for you, or if you have any
8735 problems. We gather on the IRC channel
8736 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
8737 irc.debian.org and the
8738 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
8739 mailing list
</a
>.
</p
>
8741 <p
>Once you get your freedombox operational, you can visit
8742 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
8743 welcome screen (dead end - do not be surprised if you are unable to
8744 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
8745 to look at the rest of plinth. The default user is
'admin
' and the
8746 default password is
'secret
'.
</p
>
8751 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
8752 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
8753 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
8754 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
8755 <description><p
>Earlier, I reported about
8756 <a href=
"https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
8757 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
8758 told by IBM that the original disk should be thrown away. And as
8759 there no longer was a problem if I bricked the firmware, I decided
8760 today to try to install Intel firmware to replace the Lenovo firmware
8761 currently on the disk.
</p
>
8763 <p
>I searched the Intel site for firmware, and found
8764 <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
>
8765 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
8766 according to the site should contain the latest firmware for SSD
8767 disks. I inserted the broken disk in one of my spare laptops and
8768 booted the ISO from a USB stick. The disk was recognized, but the
8769 program claimed the newest firmware already were installed and refused
8770 to insert any Intel firmware. So no change, and the disk is still
8771 unable to handle write load. :( I guess the only way to get them
8772 working would be if Lenovo releases new firmware. No idea how likely
8773 that is. Anyway, just blogging about this test for completeness. I
8774 got a working Samsung disk, and see no point in spending more time on
8775 the broken disks.
</p
>
8780 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
8781 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
8782 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
8783 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
8784 <description><p
>Today I switched to
8785 <a href=
"https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
8786 new laptop
</a
>. I
've previously written about the problems I had with
8787 my new Thinkpad X230, which was delivered with an
8788 <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
8789 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
8790 sustained writes. My hardware supplier have been very forthcoming in
8791 trying to find a solution, and after first trying with another
8792 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
8793 disk instead to fix it once and for all. The Samsung disk survived
8794 the installation of Debian with encrypted disks (filling the disk with
8795 random data during installation killed the first two), and I thus
8796 decided to trust it with my data. I have installed it as a Debian Edu
8797 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
8798 server at home using Kerberos and LDAP, and will use it as my work
8799 station from now on.
</p
>
8801 <p
>As this is a solid state disk with no moving parts, I believe the
8802 Debian Wheezy default installation need to be tuned a bit to increase
8803 performance and increase life time of the disk. The Linux kernel and
8804 user space applications do not yet adjust automatically to such
8805 environment. To make it easier for my self, I created a draft Debian
8806 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
8807 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
8808 for the ssd-setup package
</a
> is available from collab-maint, and it
8809 is set up to adjust the setup of the machine by just installing the
8810 package. If there is any non-SSD disk in the machine, the package
8811 will refuse to install, as I did not try to write any logic to sort
8812 file systems in SSD and non-SSD file systems.
</p
>
8814 <p
>I consider the package a draft, as I am a bit unsure how to best
8815 set up Debian Wheezy with an SSD. It is adjusted to my use case,
8816 where I set up the machine with one large encrypted partition (in
8817 addition to /boot), put LVM on top of this and set up partitions on
8818 top of this again. See the README file in the package source for the
8819 references I used to pick the settings. At the moment these
8820 parameters are tuned:
</p
>
8824 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
8825 (adding discard to /etc/crypttab)
</li
>
8827 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
8828 this case a cryptsetup partition) by changing issue_discards from
8829 0 to
1 in /etc/lvm/lvm.conf.
</li
>
8831 <li
>Set relatime as a file system option for ext3 and ext4 file
8834 <li
>Tell swap to use TRIM commands by adding
'discard
' to
8835 /etc/fstab.
</li
>
8837 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
8839 <li
>Run fstrim on every ext3 and ext4 file system every night (from
8840 cron.daily).
</li
>
8842 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
8843 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
8847 <p
>During installation, I cancelled the part where the installer fill
8848 the disk with random data, as this would kill the SSD performance for
8849 little gain. My goal with the encrypted file system is to ensure
8850 those stealing my laptop end up with a brick and not a working
8851 computer. I have no hope in keeping the really resourceful people
8852 from getting the data on the disk (see
8853 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
8854 Thus I concluded that adding the discard option to crypttab is the
8855 right thing to do.
</p
>
8857 <p
>I considered using the noop I/O scheduler, as several recommended
8858 it for SSD, but others recommended deadline and a benchmark I found
8859 indicated that deadline might be better for interactive use.
</p
>
8861 <p
>I also considered using the
'discard
' file system option for ext3
8862 and ext4, but read that it would give a performance hit ever time a
8863 file is removed, and thought it best to that that slowdown once a day
8864 instead of during my work.
</p
>
8866 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
8867 this is already done by Debian Edu.
</p
>
8869 <p
>I have not yet started on the user space tuning. I expect
8870 iceweasel need some tuning, and perhaps other applications too, but
8871 have not yet had time to investigate those parts.
</p
>
8873 <p
>The package should work on Ubuntu too, but I have not yet tested it
8876 <p
>As for the answer to the question in the title of this blog post,
8877 as far as I know, the only solution I know about is to replace the
8878 disk. It might be possible to flash it with Intel firmware instead of
8879 the Lenovo firmware. But I have not tried and did not want to do so
8880 without approval from Lenovo as I wanted to keep the warranty on the
8881 disk until a solution was found and they wanted the broken disks
8887 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
8888 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
8889 <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>
8890 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
8891 <description><p
>A few days ago, I wrote about
8892 <a href=
"https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
8893 problems I experienced with my new X230 and its SSD disk
</a
>, which
8894 was dying during installation because it is unable to cope with
8895 sustained write. My supplier is in contact with
8896 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
8897 replacement disk to try to fix the problem. They decided to send an
8898 identical model, so my hopes for a permanent fix was slim.
</p
>
8900 <p
>Anyway, today I got the replacement disk and tried to install
8901 Debian Edu Wheezy with encrypted disk on it. The new disk have the
8902 same firmware version as the original. This time my hope raised
8903 slightly as the installation progressed, as the original disk used to
8904 die after
4-
7% of the disk was written to, while this time it kept
8905 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
8906 died again and I was back on square one. I still do not have a new
8907 laptop with a disk I can trust. I can not live with a disk that might
8908 lock up when I download a new
8909 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
8910 other large files. I look forward to hearing from my supplier with
8911 the next proposal from Lenovo.
</p
>
8913 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
8914 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
8915 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8916 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
8917 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8918 P/N
45N8295, P0C38732.
</p
>
8920 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
8921 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
8922 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8923 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
8924 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8925 P/N
45N8295, P0C38732.
</p
>
8927 <p
>The only difference is in the first number (serial number?), ISN,
8928 SA, date and WNPP values. Mentioning all the details here in case
8929 someone is able to use the information to find a way to identify the
8930 failing disk among working ones (if any such working disk actually
8936 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
8937 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
8938 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
8939 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
8940 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
8941 Debian Edu developer gathering and Debian and Ubuntu bug squashing
8942 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
8943 member assosiation NUUG
</a
> and
8944 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
8945 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
8946 Bitraf
</a
>.
</p
>
8948 <p
>It starts
10:
00 and continue until late evening. Everyone is
8949 welcome, and there is no fee to participate. There is on the other
8950 hand limited space, and only room for
30 people. Please put your name
8951 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
8952 wiki page
</a
> if you plan to join us.
</p
>
8957 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
8958 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
8959 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
8960 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
8961 <description><p
>Half a year ago, I reported that I had to find a
8962 <a href=
"https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
8963 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
8964 time to spend on it, and it took a while to find a model I believe
8965 will do the job, but two days ago the replacement finally arrived. I
8967 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
8968 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
8969 a roaming workstation, and it seemed to work flawlessly. But my
8970 second installation with encrypted disk was not as successful. More
8971 on that below.
</p
>
8973 <p
>I had a hard time trying to track down a good laptop, as my most
8974 important requirements (robust and with a good keyboard) are never
8975 listed in the feature list. But I did get good help from the search
8976 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
8977 allowed me to limit the list of interesting laptops based on my other
8978 requirements. A bit surprising that SSD disk are not disks according
8979 to that search interface, so I had to drop specifying the number of
8980 disks from my search parameters. I also asked around among friends to
8981 get their impression on keyboards and robustness.
</p
>
8983 <p
>So the new laptop arrived, and it is quite a lot wider than the
8984 X41. I am not quite convinced about the keyboard, as it is
8985 significantly wider than my old keyboard, and I have to stretch my
8986 hand a lot more to reach the edges. But the key response is fairly
8987 good and the individual key shape is fairly easy to handle, so I hope
8988 I will get used to it. My old X40 was starting to fail, and I really
8989 needed a new laptop now. :)
</p
>
8991 <p
>Turning off the touch pad was simple. All it took was a quick
8992 visit to the BIOS during boot it disable it.
</p
>
8994 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
8995 lock up during load. And this happen when installing Debian Wheezy
8996 with encrypted disk, while the disk is being filled with random data.
8997 I also tested to install Ubuntu Raring, and it happen there too if I
8998 reenable the code to fill the disk with random data (it is disabled by
8999 default in Ubuntu). And the bug with is already known. It was
9000 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
9001 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
9002 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
9003 kernel developers as
9004 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
9005 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
9006 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
9007 Lenovo forums, both for
9008 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
9009 2012-
11-
10</a
> and for
9010 <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
9011 03-
20-
2013</a
>. The problem do not only affect installation. The
9012 reports state that the disk lock up during use if many writes are done
9013 on the disk, so it is much no use to work around the installation
9014 problem and end up with a computer that can lock up at any moment.
9016 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
9017 available
</a
> that will lock up the hard drive after running a few
9018 minutes by writing to a file.
</p
>
9020 <p
>I
've contacted my supplier and asked how to handle this, and after
9021 contacting PCHELP Norway (request
01D1FDP) which handle support
9022 requests for Lenovo, his first suggestion was to upgrade the disk
9023 firmware. Unfortunately there is no newer firmware available from
9024 Lenovo, as my disk already have the most recent one (version LF1i). I
9025 hope to hear more from him today and hope the problem can be
9031 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
9032 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
9033 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
9034 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
9035 <description><p
>Half a year ago, I reported that I had to find a replacement for my
9036 trusty old Thinkpad X41. Unfortunately I did not have much time to
9037 spend on it, but today the replacement finally arrived. I ended up
9038 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
9039 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
9040 Wheezy as a roaming workstation, and it worked flawlessly. As I write
9041 this, it is installing what I hope will be a more final installation,
9042 with a encrypted hard drive to ensure any dope head stealing it end up
9043 with an expencive door stop.
</p
>
9045 <p
>I had a hard time trying to track down a good laptop, as my most
9046 important requirements (robust and with a good keyboard) are never
9047 listed in the feature list. But I did get good help from the search
9048 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
9049 allowed me to limit the list of interesting laptops based on my other
9050 requirements. A bit surprising that SSD disk are not disks, so I had
9051 to drop number of disks from my search parameters.
</p
>
9053 <p
>I am not quite convinced about the keyboard, as it is significantly
9054 wider than my old keyboard, and I have to stretch my hand a lot more
9055 to reach the edges. But the key response is fairly good and the
9056 individual key shape is fairly easy to handle, so I hope I will get
9057 used to it. My old X40 was starting to fail, and I really needed a
9058 new laptop now. :)
</p
>
9060 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
9065 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
9066 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
9067 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
9068 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
9069 <description><p
>It annoys me when the computer fail to do automatically what it is
9070 perfectly capable of, and I have to do it manually to get things
9071 working. One such task is to find out what firmware packages are
9072 needed to get the hardware on my computer working. Most often this
9073 affect the wifi card, but some times it even affect the RAID
9074 controller or the ethernet card. Today I pushed version
0.4 of the
9075 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
9076 including a new script isenkram-autoinstall-firmware handling the
9077 process of asking all the loaded kernel modules what firmware files
9078 they want, find debian packages providing these files and install the
9079 debian packages. Here is a test run on my laptop:
</p
>
9081 <p
><pre
>
9082 # isenkram-autoinstall-firmware
9083 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
9084 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
9085 info: locating packages with the requested firmware files
9086 info: Updating APT sources after adding non-free APT source
9087 info: trying to install firmware-ipw2x00
9090 Preconfiguring packages ...
9091 Selecting previously deselected package firmware-ipw2x00.
9092 (Reading database ...
259727 files and directories currently installed.)
9093 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
9094 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
9096 </pre
></p
>
9098 <p
>When all the requested firmware is present, a simple message is
9099 printed instead:
</p
>
9101 <p
><pre
>
9102 # isenkram-autoinstall-firmware
9103 info: did not find any firmware files requested by loaded kernel modules. exiting
9105 </pre
></p
>
9107 <p
>It could use some polish, but it is already working well and saving
9108 me some time when setting up new machines. :)
</p
>
9110 <p
>So, how does it work? It look at the set of currently loaded
9111 kernel modules, and look up each one of them using modinfo, to find
9112 the firmware files listed in the module meta-information. Next, it
9113 download the Contents file from a nearby APT mirror, and search for
9114 the firmware files in this file to locate the package with the
9115 requested firmware file. If the package is in the non-free section, a
9116 non-free APT source is added and the package is installed using
9117 <tt
>apt-get install
</tt
>. The end result is a slightly better working
9120 <p
>I hope someone find time to implement a more polished version of
9121 this script as part of the hw-detect debian-installer module, to
9122 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
9123 #
655507</a
>. There really is no need to insert USB sticks with
9124 firmware during a PXE install when the packages already are available
9125 from the nearby Debian mirror.
</p
>
9130 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
9131 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
9132 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
9133 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
9134 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
9135 the screen just turn black when Linux boot, either during installation
9136 or on first boot from the hard disk. I
've seen it once in a while the
9137 last few years, but only recently understood the cause. I
've seen it
9138 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
9139 The reason seem to be in the wiring of some laptops. The system to
9140 control the screen background light is inverted, so when Linux try to
9141 turn the brightness fully on, it end up turning it off instead. I do
9142 not know which Linux drivers are affected, but this post is about the
9143 i915 driver used by the
9144 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
9145 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
9147 <p
>The problem can be worked around two ways. Either by adding
9148 i915.invert_brightness=
1 as a kernel option, or by adding a file in
9149 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
9150 option when it load the i915 kernel module. On Debian and Ubuntu, it
9151 can be done by running these commands as root:
</p
>
9154 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
9155 update-initramfs -u -k all
9158 <p
>Since March
2012 there is
9159 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
9160 mechanism in the Linux kernel
</a
> to tell the i915 driver which
9161 hardware have this problem, and get the driver to invert the
9162 brightness setting automatically. To use it, one need to add a row in
9163 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
9164 intel_quirks array
</a
> in the driver source
9165 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
9166 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
9167 number (vendor number
8086 is assumed) and subdevice vendor and device
9170 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
9171 -vvnn
</tt
> for the video card in question:
</p
>
9173 <p
><pre
>
9174 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
9175 3rd Gen Core processor Graphics Controller [
8086:
0156] \
9176 (rev
09) (prog-if
00 [VGA controller])
9177 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
9178 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
9179 ParErr- Stepping- SE RR- FastB2B- DisINTx+
9180 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
9181 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
9183 Interrupt: pin A routed to IRQ
42
9184 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
9185 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
9186 Region
4: I/O ports at
4000 [size=
64]
9187 Expansion ROM at
<unassigned
> [disabled]
9188 Capabilities:
<access denied
>
9189 Kernel driver in use: i915
9190 </pre
></p
>
9192 <p
>The resulting intel_quirks entry would then look like this:
</p
>
9194 <p
><pre
>
9195 struct intel_quirk intel_quirks[] = {
9197 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
9198 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
9201 </pre
></p
>
9203 <p
>According to the kernel module instructions (as seen using
9204 <tt
>modinfo i915
</tt
>), information about hardware needing the
9205 invert_brightness flag should be sent to the
9206 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
9207 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
9208 developers. But my email about the laptop sent
2013-
06-
03 have not
9210 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
9211 web archive for the mailing list
</a
>, so I suspect they do not accept
9212 emails from non-subscribers. Because of this, I sent my patch also to
9213 the Debian bug tracking system instead as
9214 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
9215 sure the patch is not lost.
</p
>
9217 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
9218 with this problem working properly with Linux. If you use Gnome, your
9219 worries should be over at this point. But if you use KDE, there is
9220 something in KDE ignoring the invert_brightness setting and turning on
9221 the screen during login. I
've reported it to Debian as
9222 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
9223 have no idea yet how to figure out exactly what subsystem is doing
9224 this. Perhaps you can help? Perhaps you know what the Gnome
9225 developers did to handle this, and this can give a clue to the KDE
9226 developers? Or you know where in KDE the screen brightness is changed
9227 during login? If so, please update the BTS report (or get in touch if
9228 you do not know how to update BTS).
</p
>
9230 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
9231 acpi_backlight=vendor, to disable ACPI backlight support completely,
9232 as the ACPI information on the machine is trash and it is better to
9233 leave it to the intel video driver to control the screen
9234 backlight.
</p
>
9239 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
9240 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
9241 <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>
9242 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
9243 <description><p
>Two days ago, I asked
9244 <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
9245 I could install Linux on a Packard Bell EasyNote LV computer
9246 preinstalled with Windows
8</a
>. I found a solution, but am horrified
9247 with the obstacles put in the way of Linux users on a laptop with UEFI
9248 and Windows
8.
</p
>
9250 <p
>I never found out if the cause of my problems were the use of UEFI
9251 secure booting or fast boot. I suspect fast boot was the problem,
9252 causing the firmware to boot directly from HD without considering any
9253 key presses and alternative devices, but do not know UEFI settings
9254 enough to tell.
</p
>
9256 <p
>There is no way to install Linux on the machine in question without
9257 opening the box and disconnecting the hard drive! This is as far as I
9258 can tell, the only way to get access to the firmware setup menu
9259 without accepting the Windows
8 license agreement. I am told (and
9260 found description on how to) that it is possible to configure the
9261 firmware setup once booted into Windows
8. But as I believe the terms
9262 of that agreement are completely unacceptable, accepting the license
9263 was never an alternative. I do not enter agreements I do not intend
9264 to follow.
</p
>
9266 <p
>I feared I had to return the laptops and ask for a refund, and
9267 waste many hours on this, but luckily there was a way to get it to
9268 work. But I would not recommend it to anyone planning to run Linux on
9269 it, and I have become sceptical to Windows
8 certified laptops. Is
9270 this the way Linux will be forced out of the market place, by making
9271 it close to impossible for
"normal
" users to install Linux without
9272 accepting the Microsoft Windows license terms? Or at least not
9273 without risking to loose the warranty?
</p
>
9275 <p
>I
've updated the
9276 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
9277 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
9278 do not have to struggle as much as I did to get Linux into the
9281 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
9282 Michael Tokarev and others for feedback and ideas.
</p
>
9287 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
9288 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
9289 <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>
9290 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
9291 <description><p
>I
've run into quite a problem the last few days. I bought three
9292 new laptops for my parents and a few others. I bought Packard Bell
9293 Easynote LV to run Kubuntu on and use as their home computer. But I
9294 am completely unable to figure out how to install Linux on it. The
9295 computer is preinstalled with Windows
8, and I suspect it uses UEFI
9296 instead of a BIOS to boot.
</p
>
9298 <p
>The problem is that I am unable to get it to PXE boot, and unable
9299 to get it to boot the Linux installer from my USB stick. I have yet
9300 to try the DVD install, and still hope it will work. when I turn on
9301 the computer, there is no information on what buttons to press to get
9302 the normal boot menu. I expect to get some boot menu to select PXE or
9303 USB stick booting. When booting, it first ask for the language to
9304 use, then for some regional settings, and finally if I will accept the
9305 Windows
8 terms of use. As these terms are completely unacceptable to
9306 me, I have no other choice but to turn off the computer and try again
9307 to get it to boot the Linux installer.
</p
>
9309 <p
>I have gathered my findings so far on a Linlap page about the
9310 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
9311 EasyNote LV
</a
> model. If you have any idea how to get Linux
9312 installed on this machine, please get in touch or update that wiki
9313 page. If I can
't find a way to install Linux, I will have to return
9314 the laptop to the seller and find another machine for my parents.
</p
>
9316 <p
>I wonder, is this the way Linux will be forced out of the market
9317 using UEFI and
"secure boot
" by making it impossible to install Linux
9318 on new Laptops?
</p
>
9323 <title>How to transform a Debian based system to a Debian Edu installation
</title>
9324 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
9325 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
9326 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
9327 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
9328 an operating system based on Debian intended for use in schools. It
9329 contain a turn-key solution for the computer network provided to
9330 pupils in the primary schools. It provide both the central server,
9331 network boot servers and desktop environments with heaps of
9332 educational software. The project was founded almost
12 years ago,
9333 2001-
07-
02. If you want to support the project, which is in need for
9334 cash to fund developer gatherings and other project related activity,
9335 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
9336 donate some money
</a
>.
9338 <p
>A topic that come up again and again on the Debian Edu mailing
9339 lists and elsewhere, is the question on how to transform a Debian or
9340 Ubuntu installation into a Debian Edu installation. It isn
't very
9341 hard, and last week I wrote a script to replicate the steps done by
9342 the Debian Edu installer.
</p
>
9344 <p
>The script,
9345 <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/
>
9346 in the debian-edu-config package, will go through these six steps and
9347 transform an existing Debian Wheezy or Ubuntu (untested) installation
9348 into a Debian Edu Workstation:
</p
>
9352 <li
>Add skolelinux related APT sources.
</li
>
9353 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
9354 <li
>Install debian-edu-install to load preseeding values and pull in
9355 our configuration.
</li
>
9356 <li
>Preseed debconf database with profile setup in
9357 /etc/debian-edu/config, and run tasksel to install packages
9358 according to the profile specified in the config above,
9359 overriding some of the Debian automation machinery.
</li
>
9360 <li
>Run debian-edu-cfengine-D installation to configure everything
9361 that could not be done using preseeding.
</li
>
9362 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
9366 <p
>There are some steps in the Debian Edu installation that can not be
9367 replicated like this. Disk partitioning and LVM setup, for example.
9368 So this script just assume there is enough disk space to install all
9369 the needed packages.
</p
>
9371 <p
>The script was created to help a Debian Edu student working on
9372 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
9373 Debian Edu client, and using it he can take the existing
9374 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
9375 transform it into a fully functioning Debian Edu Workstation (or
9376 Roaming Workstation, or whatever :).
</p
>
9378 <p
>The default setting in the script is to create a KDE Workstation.
9379 If a LXDE based Roaming workstation is wanted instead, modify the
9380 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
9382 <p
><pre
>
9383 PROFILE=
"Roaming-Workstation
"
9384 DESKTOP=
"lxde
"
9385 </pre
></p
>
9387 <p
>The script could even become useful to set up Debian Edu servers in
9388 the cloud, by starting with a virtual Debian installation at some
9389 virtual hosting service and setting up all the services on first
9395 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
9396 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
9397 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
9398 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
9399 <description><P
>In January,
9400 <a href=
"https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
9401 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
9402 channel #debian-lego
</a
>, for those of us in the Debian and Linux
9403 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
9404 marvellous construction system from Denmark. We also created
9405 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
9406 a place to take notes and write down our plans and hopes. And several
9407 people showed up to help. I was very happy to see the effect of my
9408 call. Since the small start, we have a debtags tag
9409 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
9410 tag for LEGO related packages, and now count
10 packages related to
9411 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
9413 <p
><table
>
9414 <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
>
9415 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
9416 <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
>
9417 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
9418 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
9419 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
9420 <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
>
9421 <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
>
9422 <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
>
9423 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
9424 </table
></p
>
9426 <p
>Some of these are available in Wheezy, and all but one are
9427 currently available in Jessie/testing. leocad is so far only
9428 available in experimental.
</p
>
9430 <p
>If you care about LEGO in Debian, please join us on IRC and help
9431 adding the rest of the great free software tools available on Linux
9432 for LEGO designers.
</p
>
9437 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
9438 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
9439 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
9440 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
9441 <description><p
>When I woke up this morning, I was very happy to see that the
9442 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
9443 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
9444 Debian release, and I expect to move my machines at home over to it fairly
9447 <p
>The new debian release contain heaps of new stuff, and one program
9448 in particular make me very happy to see included. The
9449 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
9450 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
9451 included for the first time. Alongside similar programs like
9452 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
9453 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
9454 it allow for visual programming where syntax errors can not happen,
9455 and a friendly programming environment for learning to control the
9456 computer. Scratch will also be included in the next release of Debian
9459 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
9460 Edu/Skolelinux release too. The
9461 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
9462 alpha release
</a
> went out last week, and the next should soon
9468 <title>Isenkram
0.2 finally in the Debian archive
</title>
9469 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
9470 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
9471 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
9472 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
9473 package
</a
> finally made it into the archive, after lingering in NEW
9474 for many months. I uploaded it to the Debian experimental suite
9475 2013-
01-
27, and today it was accepted into the archive.
</p
>
9477 <p
>Isenkram is a system for suggesting to users what packages to
9478 install to work with a pluggable hardware device. The suggestion pop
9479 up when the device is plugged in. For example if a Lego Mindstorm NXT
9480 is inserted, it will suggest to install the program needed to program
9481 the NXT controller. Give it a go, and report bugs and suggestions to
9487 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
9488 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
9489 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
9490 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
9491 <description><p
>My
9492 <a href=
"https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
9493 bitcoin related blog post
</a
> mentioned that the new
9494 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
9495 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
9496 2013-
01-
19, and have been available in unstable since then. It was
9497 automatically copied to Ubuntu, and is available in their Raring
9498 version too.
</p
>
9500 <p
>But there is a strange problem with the build that block this new
9501 version from being available on the i386 and kfreebsd-i386
9502 architectures. For some strange reason, the autobuilders in Debian
9503 for these architectures fail to run the test suite on these
9504 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
9505 We are so far unable to reproduce it when building it manually, and
9506 no-one have been able to propose a fix. If you got an idea what is
9507 failing, please let us know via the BTS.
</p
>
9509 <p
>One feature that is annoying me with of the bitcoin client, because
9510 I often run low on disk space, is the fact that the client will exit
9511 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
9512 #
696715</a
>). So make sure you have enough disk space when you run
9515 <p
>As usual, if you use bitcoin and want to show your support of my
9516 activities, please send Bitcoin donations to my address
9517 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9522 <title>Welcome to the world, Isenkram!
</title>
9523 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
9524 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
9525 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
9526 <description><p
>Yesterday, I
9527 <a href=
"https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
9528 for testers
</a
> for my prototype for making Debian better at handling
9529 pluggable hardware devices, which I
9530 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
9531 out to create
</a
> earlier this month. Several valuable testers showed
9532 up, and caused me to really want to to open up the development to more
9533 people. But before I did this, I want to come up with a sensible name
9534 for this project. Today I finally decided on a new name, and I have
9535 renamed the project from hw-support-handler to this new name. In the
9536 process, I moved the source to git and made it available as a
9537 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
9538 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
9539 To fetch and build the latest version of the source, use
</p
>
9542 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
9543 cd isenkram
&& git-buildpackage -us -uc
9546 <p
>I have not yet adjusted all files to use the new name yet. If you
9547 want to hack on the source or improve the package, please go ahead.
9548 But please talk to me first on IRC or via email before you do major
9549 changes, to make sure we do not step on each others toes. :)
</p
>
9551 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
9552 stuff, typically meaning tools, nails, screws, etc. Typical hardware
9553 stuff, in other words. I
've been told it is the Norwegian variant of
9554 the German word eisenkram, for those that are familiar with that
9557 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
9558 instructions, to avoid confusing people with an error from the signing
9561 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
9562 clone argument to avoid the need for authentication.
</p
>
9567 <title>First prototype ready making hardware easier to use in Debian
</title>
9568 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
9569 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
9570 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
9571 <description><p
>Early this month I set out to try to
9572 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
9573 the Debian support for pluggable hardware devices
</a
>. Now my
9574 prototype is working, and it is ready for a larger audience. To test
9576 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
9577 from the Debian Edu subversion repository
</a
>, build and install the
9578 package. You might have to log out and in again activate the
9579 autostart script.
</p
>
9581 <p
>The design is simple:
</p
>
9585 <li
>Add desktop entry in /usr/share/autostart/ causing a program
9586 hw-support-handlerd to start when the user log in.
</li
>
9588 <li
>This program listen for kernel events about new hardware (directly
9589 from the kernel like udev does), not using HAL dbus events as I
9590 initially did.
</li
>
9592 <li
>When new hardware is inserted, look up the hardware modalias in
9593 the APT database, a database
9594 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
9595 via HTTP
</a
> and a database available as part of the package.
</li
>
9597 <li
>If a package is mapped to the hardware in question, the package
9598 isn
't installed yet and this is the first time the hardware was
9599 plugged in, show a desktop notification suggesting to install the
9600 package or packages.
</li
>
9602 <li
>If the user click on the
'install package now
' button, ask
9603 aptdaemon via the PackageKit API to install the requrired package.
</li
>
9605 <li
>aptdaemon ask for root password or sudo password, and install the
9606 package while showing progress information in a window.
</li
>
9610 <p
>I still need to come up with a better name for the system. Here
9611 are some screen shots showing the prototype in action. First the
9612 notification, then the password request, and finally the request to
9613 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
9615 <p
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
9616 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
9617 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
9618 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
9619 <br
><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
9621 <p
>The prototype still need to be improved with longer timeouts, but
9622 is already useful. The database of hardware to package mappings also
9623 need more work. It is currently compatible with the Ubuntu way of
9624 storing such information in the package control file, but could be
9625 changed to use other formats instead or in addition to the current
9626 method. I
've dropped the use of discover for this mapping, as the
9627 modalias approach is more flexible and easier to use on Linux as long
9628 as the Linux kernel expose its modalias strings directly.
</p
>
9630 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
9631 here is the command required to check out and build the source: Use
9632 '<tt
>svn checkout
9633 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
9634 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
9635 devscripts package.
</p
>
9637 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
9638 renamed to Isenkram and the source moved from the Debian Edu
9639 subversion repository to a Debian collab-maint git repository. See
9640 <a href=
"https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
9641 instructions
</a
> for details.
</p
>
9646 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
9647 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
9648 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
9649 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
9650 <description><p
>This Christmas my trusty old laptop died. It died quietly and
9651 suddenly in bed. With a quiet whimper, it went completely quiet and
9652 black. The power button was no longer able to turn it on. It was a
9653 IBM Thinkpad X41, and the best laptop I ever had. Better than both
9654 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
9655 Compaq I had before that. Now I need to find a replacement. To keep
9656 going during Christmas, I moved the one year old SSD disk to my old
9657 X40 where it fitted (only one I had left that could use it), but it is
9658 not a durable solution.
9660 <p
>My laptop needs are fairly modest. This is my wishlist from when I
9661 got a new one more than
10 years ago. It still holds true.:)
</p
>
9665 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
9666 than A4).
</li
>
9667 <li
>Robust, it will be in my backpack every day.
</li
>
9668 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
9669 <li
>Long battery life time. Preferable a week.
</li
>
9670 <li
>Internal WIFI network card.
</li
>
9671 <li
>Internal Twisted Pair network card.
</li
>
9672 <li
>Some USB slots (
2-
3 is plenty)
</li
>
9673 <li
>Good keyboard - similar to the Thinkpad.
</li
>
9674 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
9676 <li
>Hardware supported by Debian Stable, ie the default kernel and
9677 X.org packages.
</li
>
9678 <li
>Quiet, preferably fan free (or at least not using the fan most of
9683 <p
>You will notice that there are no RAM and CPU requirements in the
9684 list. The reason is simply that the specifications on laptops the
9685 last
10-
15 years have been sufficient for my needs, and I have to look
9686 at other features to choose my laptop. But are there still made as
9687 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
9688 robust, and Thinkpads seem to be heading in the wrong direction since
9689 Lenovo took over. But I
've been told that X220 and X1 Carbon might
9690 still be useful.
</p
>
9692 <p
>Perhaps I should rethink my needs, and look for a pad with an
9693 external keyboard? I
'll have to check the
9694 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
9695 well-supported laptops, or perhaps just buy one preinstalled from one
9696 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
9697 Pre-loaded site
</a
>.
</p
>
9702 <title>How to find a browser plugin supporting a given MIME type
</title>
9703 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
9704 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
9705 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
9706 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
9707 install to get support for a given MIME type. Thanks to
9708 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
9709 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
9710 Unfortunately, not very many packages provide the needed meta
9711 information, Anyway, here is a small script to look up all browser
9712 plugin packages announcing ther MIME support using this specification:
</p
>
9718 def pkgs_handling_mimetype(mimetype):
9723 version = pkg.candidate
9725 version = pkg.installed
9728 record = version.record
9729 if not record.has_key(
'Npp-MimeType
'):
9731 mime_types = record[
'Npp-MimeType
'].split(
',
')
9732 for t in mime_types:
9733 t = t.rstrip().strip()
9735 thepkgs.append(pkg.name)
9737 mimetype =
"audio/ogg
"
9738 if
1 < len(sys.argv):
9739 mimetype = sys.argv[
1]
9740 print
"Browser plugin packages supporting %s:
" % mimetype
9741 for pkg in pkgs_handling_mimetype(mimetype):
9742 print
" %s
" %pkg
9745 <p
>It can be used like this to look up a given MIME type:
</p
>
9748 % ./apt-find-browserplug-for-mimetype
9749 Browser plugin packages supporting audio/ogg:
9751 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
9752 Browser plugin packages supporting application/x-shockwave-flash:
9753 browser-plugin-gnash
9757 <p
>In Ubuntu this mechanism is combined with support in the browser
9758 itself to query for plugins and propose to install the needed
9759 packages. It would be great if Debian supported such feature too. Is
9760 anyone working on adding it?
</p
>
9762 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
9763 request for icweasel support for this feature is
9764 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
9765 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
9766 of manpower and wish for a different design is the reason thus feature
9767 is not yet in iceweasel from Debian.
</p
>
9772 <title>What is the most supported MIME type in Debian?
</title>
9773 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
9774 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
9775 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
9776 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
9777 proposal to add AppStream information to the Debian archive
</a
>, is a
9778 proposal to make it possible for a Desktop application to propose to
9779 the user some package to install to gain support for a given MIME
9780 type, font, library etc. that is currently missing. With such
9781 mechanism in place, it would be possible for the desktop to
9782 automatically propose and install leocad if some LDraw file is
9783 downloaded by the browser.
</p
>
9785 <p
>To get some idea about the current content of the archive, I decided
9786 to write a simple program to extract all .desktop files from the
9787 Debian archive and look up the claimed MIME support there. The result
9789 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
9790 site
</a
>. Using the collected information, it become possible to
9791 answer the question in the title. Here are the
20 most supported MIME
9792 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
9793 The complete list is available from the link above.
</p
>
9795 <p
><strong
>Debian Stable:
</strong
></p
>
9799 ----- -----------------------
9815 18 application/x-ogg
9822 <p
><strong
>Debian Testing:
</strong
></p
>
9826 ----- -----------------------
9842 18 application/x-ogg
9849 <p
><strong
>Debian Unstable:
</strong
></p
>
9853 ----- -----------------------
9870 18 application/x-ogg
9876 <p
>I am told that PackageKit can provide an API to access the kind of
9877 information mentioned in DEP-
11. I have not yet had time to look at
9878 it, but hope the PackageKit people in Debian are on top of these
9881 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
9882 discovering a typo in my script.
</p
>
9887 <title>Using modalias info to find packages handling my hardware
</title>
9888 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
9889 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
9890 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
9891 <description><p
>Yesterday, I wrote about the
9892 <a href=
"https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
9893 values provided by the Linux kernel
</a
> following my hope for
9894 <a href=
"https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
9895 dongle support in Debian
</a
>. Using this knowledge, I have tested how
9896 modalias values attached to package names can be used to map packages
9897 to hardware. This allow the system to look up and suggest relevant
9898 packages when I plug in some new hardware into my machine, and replace
9899 discover and discover-data as the database used to map hardware to
9902 <p
>I create a modaliases file with entries like the following,
9903 containing package name, kernel module name (if relevant, otherwise
9904 the package name) and globs matching the relevant hardware
9907 <p
><blockquote
>
9908 Package: package-name
9909 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
9910 </blockquote
></p
>
9912 <p
>It is fairly trivial to write code to find the relevant packages
9913 for a given modalias value using this file.
</p
>
9915 <p
>An entry like this would suggest the video and picture application
9916 cheese for many USB web cameras (interface bus class
0E01):
</p
>
9918 <p
><blockquote
>
9920 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
9921 </blockquote
></p
>
9923 <p
>An entry like this would suggest the pcmciautils package when a
9924 CardBus bridge (bus class
0607) PCI device is present:
</p
>
9926 <p
><blockquote
>
9927 Package: pcmciautils
9928 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
9929 </blockquote
></p
>
9931 <p
>An entry like this would suggest the package colorhug-client when
9932 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
9934 <p
><blockquote
>
9935 Package: colorhug-client
9936 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
9937 </blockquote
></p
>
9939 <p
>I believe the format is compatible with the format of the Packages
9940 file in the Debian archive. Ubuntu already uses their Packages file
9941 to store their mappings from packages to hardware.
</p
>
9943 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
9944 announce the hardware it support in a way my prototype understand.
9945 This allow those publishing packages in an APT source outside the
9946 Debian archive as well as those backporting packages to make sure the
9947 hardware mapping are included in the package meta information. I
've
9948 tested such header in the pymissile package, and its modalias mapping
9949 is working as it should with my prototype. It even made it to Ubuntu
9952 <p
>To test if it was possible to look up supported hardware using only
9953 the shell tools available in the Debian installer, I wrote a shell
9954 implementation of the lookup code. The idea is to create files for
9955 each modalias and let the shell do the matching. Please check out and
9957 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
9958 shell script. It run without any extra dependencies and fetch the
9959 hardware mappings from the Debian archive and the subversion
9960 repository where I currently work on my prototype.
</p
>
9962 <p
>When I use it on a machine with a yubikey inserted, it suggest to
9963 install yubikey-personalization:
</p
>
9965 <p
><blockquote
>
9966 % ./hw-support-lookup
9967 <br
>yubikey-personalization
9969 </blockquote
></p
>
9971 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
9972 propose to install the pcmciautils package:
</p
>
9974 <p
><blockquote
>
9975 % ./hw-support-lookup
9976 <br
>pcmciautils
9978 </blockquote
></p
>
9980 <p
>If you know of any hardware-package mapping that should be added to
9981 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
9982 database
</a
>, please tell me about it.
</p
>
9984 <p
>It could be possible to generate several of the mappings between
9985 packages and hardware. One source would be to look at packages with
9986 kernel modules, ie packages with *.ko files in /lib/modules/, and
9987 extract their modalias information. Another would be to look at
9988 packages with udev rules, ie packages with files in
9989 /lib/udev/rules.d/, and extract their vendor/model information to
9990 generate a modalias matching rule. I have not tested any of these to
9991 see if it work.
</p
>
9993 <p
>If you want to help implementing a system to let us propose what
9994 packages to install when new hardware is plugged into a Debian
9995 machine, please send me an email or talk to me on
9996 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
10001 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
10002 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
10003 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
10004 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
10005 <description><p
>While looking into how to look up Debian packages based on hardware
10006 information, to find the packages that support a given piece of
10007 hardware, I refreshed my memory regarding modalias values, and decided
10008 to document the details. Here are my findings so far, also available
10010 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
10011 Debian Edu subversion repository
</a
>:
10013 <p
><strong
>Modalias decoded
</strong
></p
>
10015 <p
>This document try to explain what the different types of modalias
10016 values stands for. It is in part based on information from
10017 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
10018 &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;,
10019 &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
10020 &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;.
10022 <p
>The modalias entries for a given Linux machine can be found using
10023 this shell script:
</p
>
10026 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
10029 <p
>The supported modalias globs for a given kernel module can be found
10030 using modinfo:
</p
>
10033 % /sbin/modinfo psmouse | grep alias:
10034 alias: serio:ty05pr*id*ex*
10035 alias: serio:ty01pr*id*ex*
10039 <p
><strong
>PCI subtype
</strong
></p
>
10041 <p
>A typical PCI entry can look like this. This is an Intel Host
10042 Bridge memory controller:
</p
>
10044 <p
><blockquote
>
10045 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
10046 </blockquote
></p
>
10048 <p
>This represent these values:
</p
>
10051 v
00008086 (vendor)
10052 d
00002770 (device)
10053 sv
00001028 (subvendor)
10054 sd
000001AD (subdevice)
10056 sc
00 (bus subclass)
10060 <p
>The vendor/device values are the same values outputted from
'lspci
10061 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
10062 0600. The
0600 class is a host bridge. Other useful bus values are
10063 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
10065 <p
>Not sure how to figure out the interface value, nor what it
10068 <p
><strong
>USB subtype
</strong
></p
>
10070 <p
>Some typical USB entries can look like this. This is an internal
10071 USB hub in a laptop:
</p
>
10073 <p
><blockquote
>
10074 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
10075 </blockquote
></p
>
10077 <p
>Here is the values included in this alias:
</p
>
10080 v
1D6B (device vendor)
10081 p
0001 (device product)
10083 dc
09 (device class)
10084 dsc
00 (device subclass)
10085 dp
00 (device protocol)
10086 ic
09 (interface class)
10087 isc
00 (interface subclass)
10088 ip
00 (interface protocol)
10091 <p
>The
0900 device class/subclass means hub. Some times the relevant
10092 class is in the interface class section. For a simple USB web camera,
10093 these alias entries show up:
</p
>
10095 <p
><blockquote
>
10096 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
10097 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
10098 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
10099 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
10100 </blockquote
></p
>
10102 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
10103 camera),
0101 is audio control device and
0102 is audio streaming (aka
10104 microphone). Thus this is a camera with microphone included.
</p
>
10106 <p
><strong
>ACPI subtype
</strong
></p
>
10108 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
10109 receiver in a Thinkpad X40:
</p
>
10111 <p
><blockquote
>
10112 acpi:IBM0071:PNP0511:
10113 </blockquote
></p
>
10115 <p
>The values between the colons are IDs.
</p
>
10117 <p
><strong
>DMI subtype
</strong
></p
>
10119 <p
>The DMI table contain lots of information about the computer case
10120 and model. This is an entry for a IBM Thinkpad X40, fetched from
10121 /sys/devices/virtual/dmi/id/modalias:
</p
>
10123 <p
><blockquote
>
10124 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
10125 </blockquote
></p
>
10127 <p
>The values present are
</p
>
10130 bvn IBM (BIOS vendor)
10131 bvr
1UETB
6WW(
1.66) (BIOS version)
10132 bd
06/
15/
2005 (BIOS date)
10133 svn IBM (system vendor)
10134 pn
2371H4G (product name)
10135 pvr ThinkPadX40 (product version)
10136 rvn IBM (board vendor)
10137 rn
2371H4G (board name)
10138 rvr NotAvailable (board version)
10139 cvn IBM (chassis vendor)
10140 ct
10 (chassis type)
10141 cvr NotAvailable (chassis version)
10144 <p
>The chassis type
10 is Notebook. Other interesting values can be
10145 found in the dmidecode source:
</p
>
10149 4 Low Profile Desktop
10162 17 Main Server Chassis
10163 18 Expansion Chassis
10165 20 Bus Expansion Chassis
10166 21 Peripheral Chassis
10168 23 Rack Mount Chassis
10177 <p
>The chassis type values are not always accurately set in the DMI
10178 table. For example my home server is a tower, but the DMI modalias
10179 claim it is a desktop.
</p
>
10181 <p
><strong
>SerIO subtype
</strong
></p
>
10183 <p
>This type is used for PS/
2 mouse plugs. One example is from my
10184 test machine:
</p
>
10186 <p
><blockquote
>
10187 serio:ty01pr00id00ex00
10188 </blockquote
></p
>
10190 <p
>The values present are
</p
>
10199 <p
>This type is supported by the psmouse driver. I am not sure what
10200 the valid values are.
</p
>
10202 <p
><strong
>Other subtypes
</strong
></p
>
10204 <p
>There are heaps of other modalias subtypes according to
10205 file2alias.c. There is the rest of the list from that source: amba,
10206 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
10207 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
10208 vmbus, x86cpu and zorro. I did not spend time documenting all of
10209 these, as they do not seem relevant for my intended use with mapping
10210 hardware to packages when new stuff is inserted during run time.
</p
>
10212 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
10214 <p
>To check which kernel modules provide support for a given modalias,
10215 one can use the following shell script:
</p
>
10218 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
10219 echo
"$id
" ; \
10220 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
10224 <p
>The output can look like this (only the first few entries as the
10225 list is very long on my test machine):
</p
>
10229 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
10231 FATAL: Module acpi:device: not found.
10233 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
10234 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
10235 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
10236 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
10237 acpi:IBM0071:PNP0511:
10238 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
10239 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
10240 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
10244 <p
>If you want to help implementing a system to let us propose what
10245 packages to install when new hardware is plugged into a Debian
10246 machine, please send me an email or talk to me on
10247 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
10249 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
10250 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
10251 in /sys/ with space in them.
</p
>
10256 <title>Moved the pymissile Debian packaging to collab-maint
</title>
10257 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
10258 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
10259 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
10260 <description><p
>As part of my investigation on how to improve the support in Debian
10261 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
10262 Launcher and updated the Debian package
10263 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
10264 sure udev will fix the device permissions when it is plugged in. I
10265 also added a
"Modaliases
" header to test it in the Debian archive and
10266 hopefully make the package be proposed by jockey in Ubuntu when a user
10267 plug in his rocket launcher. In the process I moved the source to a
10268 git repository under collab-maint, to make it easier for any DD to
10269 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
10270 is not very active, but the software still work for me even after five
10271 years of relative silence. The new git repository is not listed in
10272 the uploaded package yet, because I want to test the other changes a
10273 bit more before I upload the new version. If you want to check out
10274 the new version with a .desktop file included, visit the
10275 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
10276 view
</a
> or use
"<tt
>git clone
10277 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
10282 <title>Lets make hardware dongles easier to use in Debian
</title>
10283 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
10284 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
10285 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
10286 <description><p
>One thing that annoys me with Debian and Linux distributions in
10287 general, is that there is a great package management system with the
10288 ability to automatically install software packages by downloading them
10289 from the distribution mirrors, but no way to get it to automatically
10290 install the packages I need to use the hardware I plug into my
10291 machine. Even if the package to use it is easily available from the
10292 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
10293 suggest to automatically install the python-nxt, nbc and t2n packages
10294 I need to talk to it. When I plug in a Yubikey, it could propose the
10295 yubikey-personalization package. The information required to do this
10296 is available, but no-one have pulled all the pieces together.
</p
>
10298 <p
>Some years ago, I proposed to
10299 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
10300 the discover subsystem to implement this
</a
>. The idea is fairly
10305 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
10306 starting when a user log in.
</li
>
10308 <li
>Set this program up to listen for kernel events emitted when new
10309 hardware is inserted into the computer.
</li
>
10311 <li
>When new hardware is inserted, look up the hardware ID in a
10312 database mapping to packages, and take note of any non-installed
10313 packages.
</li
>
10315 <li
>Show a message to the user proposing to install the discovered
10316 package, and make it easy to install it.
</li
>
10320 <p
>I am not sure what the best way to implement this is, but my
10321 initial idea was to use dbus events to discover new hardware, the
10322 discover database to find packages and
10323 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
10324 packages.
</p
>
10326 <p
>Yesterday, I found time to try to implement this idea, and the
10327 draft package is now checked into
10328 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
10329 Debian Edu subversion repository
</a
>. In the process, I updated the
10330 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
10331 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
10332 the relevant packages in Debian, and uploaded a new version
10333 2.2013.01.09 to unstable. I also discovered that the current
10334 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
10335 package in Debian no longer discovered any USB devices, because
10336 /proc/bus/usb/devices is no longer present. I ported it to use
10337 libusb as a fall back option to get it working. The fixed package
10338 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
10339 because of the freeze).
</p
>
10341 <p
>With this prototype in place, I can insert my Yubikey, and get this
10342 desktop notification to show up (only once, the first time it is
10343 inserted):
</p
>
10345 <p align=
"center
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
10347 <p
>For this prototype to be really useful, some way to automatically
10348 install the proposed packages by pressing the
"Please install
10349 program(s)
" button should to be implemented.
</p
>
10351 <p
>If this idea seem useful to you, and you want to help make it
10352 happen, please help me update the discover-data database with mappings
10353 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
10354 list the package you would like to have installed when a given
10355 hardware device is inserted into your computer, and report bugs using
10356 reportbug if it isn
't. Or, if you know of a better way to provide
10357 such mapping, please let me know.
</p
>
10359 <p
>This prototype need more work, and there are several questions that
10360 should be considered before it is ready for production use. Is dbus
10361 the correct way to detect new hardware? At the moment I look for HAL
10362 dbus events on the system bus, because that is the events I could see
10363 on my Debian Squeeze KDE desktop. Are there better events to use?
10364 How should the user be notified? Is the desktop notification
10365 mechanism the best option, or should the background daemon raise a
10366 popup instead? How should packages be installed? When should they
10367 not be installed?
</p
>
10369 <p
>If you want to help getting such feature implemented in Debian,
10370 please send me an email. :)
</p
>
10375 <title>New IRC channel for LEGO designers using Debian
</title>
10376 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
10377 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
10378 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
10379 <description><p
>During Christmas, I have worked a bit on the Debian support for
10380 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
10381 NXT
</a
>. My son and I have played a bit with my NXT set, and I
10382 discovered I had to build all the tools myself because none were
10383 already in Debian Squeeze. If Debian support for LEGO is something
10384 you care about, please join me on the IRC channel
10385 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
10386 irc.debian.org). There is a lot that could be done to improve the
10387 Debian support for LEGO designers. For example both CAD software
10388 and Mindstorm compilers are missing. :)
</p
>
10390 <p
>Update
2012-
01-
03: A
10391 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
10392 including links to Lego related packages is now available.
</p
>
10397 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
10398 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
10399 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
10400 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
10401 <description><p
>Let me start by wishing you all marry Christmas and a happy new
10402 year! I hope next year will prove to be a good year.
</p
>
10404 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
10405 decentralised
"currency
" that allow people to transfer bitcoins
10406 between each other with minimal overhead, is a very interesting
10407 experiment. And as I wrote a few days ago, the bitcoin situation in
10408 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
10409 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
10410 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
10411 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
10412 for one of the ftpmasters to approve the new bitcoin-qt package
10415 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
10416 team in Debian, you can easily test the package in Debian Squeeze
10417 using the following steps to get a set of working packages:
</p
>
10419 <blockquote
><pre
>
10420 git clone git://git.debian.org/git/collab-maint/bitcoin
10422 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
10423 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
10424 </pre
></blockquote
>
10426 <p
>You might have to install some build dependencies as well. The
10427 list of commands should give you two packages, bitcoind and
10428 bitcoin-qt, ready for use in a Squeeze environment. Note that the
10429 client will download the complete set of bitcoin
"blocks
", which need
10430 around
5.6 GiB of data on my machine at the moment. Make sure your
10431 ~/.bitcoin/ directory have lots of spare room if you want to download
10432 all the blocks. The client will warn if the disk is getting full, so
10433 there is not really a problem if you got too little room, but you will
10434 not be able to get all the features out of the client.
</p
>
10436 <p
>As usual, if you use bitcoin and want to show your support of my
10437 activities, please send Bitcoin donations to my address
10438 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
10443 <title>A word on bitcoin support in Debian
</title>
10444 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
10445 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
10446 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
10447 <description><p
>It has been a while since I wrote about
10448 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
10449 peer-to-peer based crypto-currency, and the reason is simply that I
10450 have been busy elsewhere. But two days ago, I started looking at the
10451 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
10452 Debian
</a
> again to try to recover my old bitcoin wallet. The package
10453 is now maintained by a
10454 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
10455 people
</a
>, and the grunt work had already been done by this team. We
10456 owe a huge thank you to all these team members. :)
10457 But I was sad to discover that the bitcoin client is missing in
10458 Wheezy. It is only available in Sid (and an outdated client from
10459 backports). The client had several RC bugs registered in BTS blocking
10460 it from entering testing. To try to help the team and improve the
10461 situation, I spent some time providing patches and triaging the bug
10462 reports. I also had a look at the bitcoin package available from Matt
10464 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
10465 Ubuntu
</a
>, and moved the useful pieces from that version into the
10466 Debian package.
</p
>
10468 <p
>After checking with the main package maintainer Jonas Smedegaard on
10469 IRC, I pushed several patches into the collab-maint git repository to
10470 improve the package. It now contains fixes for the RC issues (not from
10471 me, but fixed by Scott Howard), build rules for a Qt GUI client
10472 package, konqueror support for the bitcoin: URI and bash completion
10473 setup. As I work on Debian Squeeze, I also created
10474 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
10475 patch to backport
</a
> the latest version. Jonas is going to look at
10476 it and try to integrate it into the git repository before uploading a
10477 new version to unstable.
10479 <p
>I would very much like bitcoin to succeed, to get rid of the
10480 centralized control currently exercised in the monetary system. I
10481 find it completely unacceptable that the USA government is collecting
10482 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
10483 that the major credit card companies can block legal money
10484 transactions to Wikileaks. But for bitcoin to succeed, more people
10485 need to use bitcoins, and more people need to accept bitcoins when
10486 they sell products and services. Improving the bitcoin support in
10487 Debian is a small step in the right direction, but not enough.
10488 Unfortunately the user experience when browsing the web and wanting to
10489 pay with bitcoin is still not very good. The bitcoin: URI is a step
10490 in the right direction, but need to work in most or every browser in
10491 use. Also the bitcoin-qt client is too heavy to fire up to do a
10492 quick transaction. I believe there are other clients available, but
10493 have not tested them.
</p
>
10496 <a href=
"https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
10497 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
10498 I received
20.15 BTC so far on the address I provided in my blog two
10499 years ago, as can be
10500 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
10501 on the blockexplorer service
</a
>. Thank you everyone for your
10502 donation. The blockexplorer service demonstrates quite well that
10503 bitcoin is not quite anonymous and untracked. :) I wonder if the
10504 number of users have gone up since then. If you use bitcoin and want
10505 to show your support of my activity, please send Bitcoin donations to
10506 the same address as last time,
10507 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
10512 <title>Git repository for song book for Computer Scientists
</title>
10513 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
10514 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
10515 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
10516 <description><p
>As I
10517 <a href=
"https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
10518 this summer
</a
>, I have created a Computer Science song book a few
10519 years ago, and today I finally found time to create a public
10520 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
10521 repository for the project
</a
>.
</p
>
10523 <p
>If you want to help out, please clone the source and submit patches
10524 to the HTML version. To generate the PDF and PostScript version,
10525 please use prince XML, or let me know about a useful free software
10526 processor capable of creating a good looking PDF from the HTML.
</p
>
10528 <p
>Want to sing? You can still find the song book in HTML, PDF and
10529 PostScript formats at
10530 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
10531 Science Songbook
</a
>.
</p
>
10536 <title>Gratulerer med
19-årsdagen, Debian!
</title>
10537 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
10538 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
10539 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
10540 <description><p
>I dag fyller
10541 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
10542 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
10543 si gratulerer med dagen, Debian!
</p
>
10548 <title>Song book for Computer Scientists
</title>
10549 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
10550 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
10551 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
10552 <description><p
>Many years ago, while studying Computer Science at the
10553 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
10554 collecting computer related songs for use at parties. The original
10555 version was written in LaTeX, but a few years ago I got help from
10556 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
10557 while keeping the ability to create a nice book in PDF format. I have
10558 not had time to maintain the book for a while now, and guess I should
10559 put it up on some public version control repository where others can
10560 help me extend and update the book. If anyone is volunteering to help
10561 me with this, send me an email. Also let me know if there are songs
10562 missing in my book.
</p
>
10564 <p
>I have not mentioned the book on my blog so far, and it occured to
10565 me today that I really should let all my readers share the joys of
10566 singing out load about programming, computers and computer networks.
10567 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
10568 12</a
> is about to start (and I am not going). Want to sing? Check
10569 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
10570 Computer Science Songbook
</a
>.
10575 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
10576 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
10577 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
10578 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
10579 <description><p
>At work we have heaps of servers. I believe the total count is
10580 around
1000 at the moment. To be able to get help from the vendors
10581 when something go wrong, we want to keep the firmware on the servers
10582 up to date. If the firmware isn
't the latest and greatest, the
10583 vendors typically refuse to start debugging any problems until the
10584 firmware is upgraded. So before every reboot, we want to upgrade the
10585 firmware, and we would really like everyone handling servers at the
10586 university to do this themselves when they plan to reboot a machine.
10587 For that to happen we at the unix server admin group need to provide
10588 the tools to do so.
</p
>
10590 <p
>To make firmware upgrading easier, I am working on a script to
10591 fetch and install the latest firmware for the servers we got. Most of
10592 our hardware are from Dell and HP, so I have focused on these servers
10593 so far. This blog post is about the Dell part.
</P
>
10595 <p
>On the Dell FTP site I was lucky enough to find
10596 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
10597 with firmware information for all
11th generation servers, listing
10598 which firmware should be used on a given model and where on the FTP
10599 site I can find it. Using a simple perl XML parser I can then
10600 download the shell scripts Dell provides to do firmware upgrades from
10601 within Linux and reboot when all the firmware is primed and ready to
10602 be activated on the first reboot.
</p
>
10604 <p
>This is the Dell related fragment of the perl code I am working on.
10605 Are there anyone working on similar tools for firmware upgrading all
10606 servers at a site? Please get in touch and lets share resources.
</p
>
10608 <p
><pre
>
10612 use File::Temp qw(tempdir);
10614 # Install needed RHEL packages if missing
10615 my %rhelmodules = (
10616 'XML::Simple
' =
> 'perl-XML-Simple
',
10618 for my $module (keys %rhelmodules) {
10619 eval
"use $module;
";
10621 my $pkg = $rhelmodules{$module};
10622 system(
"yum install -y $pkg
");
10623 eval
"use $module;
";
10627 my $errorsto =
'pere@hungry.com
';
10633 sub run_firmware_script {
10634 my ($opts, $script) = @_;
10636 print STDERR
"fail: missing script name\n
";
10639 print STDERR
"Running $script\n\n
";
10641 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
10642 print STDERR
"success: firmware script ran succcessfully\n
";
10644 print STDERR
"fail: firmware script returned error\n
";
10648 sub run_firmware_scripts {
10649 my ($opts, @dirs) = @_;
10650 # Run firmware packages
10651 for my $dir (@dirs) {
10652 print STDERR
"info: Running scripts in $dir\n
";
10653 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
10654 while (my $s = readdir $dh) {
10655 next if $s =~ m/^\.\.?/;
10656 run_firmware_script($opts,
"$dir/$s
");
10664 print STDERR
"info: Downloading $url\n
";
10665 system(
"wget --quiet \
"$url\
"");
10670 my $product = `dmidecode -s system-product-name`;
10673 if ($product =~ m/PowerEdge/) {
10675 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
10676 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
10678 my $tmpdir = tempdir(
10682 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
10683 system(
'gunzip Catalog.xml.gz
');
10684 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
10685 # -q is quiet, disabling interactivity and reducing console output
10686 my $fwopts =
"-q
";
10688 for my $url (@paths) {
10689 fetch_dell_fw($url);
10691 run_firmware_scripts($fwopts, $tmpdir);
10693 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
10694 print STDERR
"error: Please report to $errorsto.\n
";
10696 chdir(
'/
');
10698 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
10699 print STDERR
"error: Please report to $errorsto.\n
";
10703 sub fetch_dell_fw {
10705 my $url =
"ftp://ftp.us.dell.com/$path
";
10709 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
10710 # firmware packages to download from Dell. Only work for Linux
10711 # machines and
11th generation Dell servers.
10712 sub fetch_dell_fw_list {
10713 my $filename = shift;
10715 my $product = `dmidecode -s system-product-name`;
10717 my ($mybrand, $mymodel) = split(/\s+/, $product);
10719 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
10721 my $xml = XMLin($filename);
10723 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
10724 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
10725 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
10727 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
10728 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
10730 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
10732 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
10734 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
10737 for my $component (@{$xml-
>{SoftwareComponent}}) {
10738 my $componenttype = $component-
>{ComponentType}-
>{value};
10740 # Drop application packages, only firmware and BIOS
10741 next if
'APAC
' eq $componenttype;
10743 my $cpath = $component-
>{path};
10744 for my $path (@paths) {
10745 if ($cpath =~ m%/$path$%) {
10746 push(@paths, $cpath);
10754 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
10755 it could work on other platforms with some tweaking. Anyone know a
10756 index like Catalog.xml is available from HP for HP servers? At the
10757 moment I maintain a similar list manually and it is quickly getting
10758 outdated.
</p
>
10763 <title>How is booting into runlevel
1 different from single user boots?
</title>
10764 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
10765 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
10766 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
10767 <description><p
>Wouter Verhelst have some
10768 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
10769 comments and opinions
</a
> on my blog post on
10770 <a href=
"https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
10771 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
10772 <a href=
"https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
10773 default KDE desktop in Debian
</a
>. I only have time to address one
10774 small piece of his comment now, and though it best to address the
10775 misunderstanding he bring forward:
</p
>
10777 <p
><blockquote
>
10778 Currently, a system admin has four options: [...] boot to a
10779 single-user system (by adding
'single
' to the kernel command line;
10780 this runs rcS and rc1 scripts)
10781 </blockquote
></p
>
10783 <p
>This make me believe Wouter believe booting into single user mode
10784 and booting into runlevel
1 is the same. I am not surprised he
10785 believe this, because it would make sense and is a quite sensible
10786 thing to believe. But because the boot in Debian is slightly broken,
10787 runlevel
1 do not work properly and it isn
't the same as single user
10788 mode. I
'll try to explain what is actually happing, but it is a bit
10789 hard to explain.
</p
>
10791 <p
>Single user mode is defined like this in /etc/inittab:
10792 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
10793 executed in single user mode is sulogin. Single user mode is a boot
10794 state
"between
" the runlevels, and when booting into single user mode,
10795 only the scripts in /etc/rcS.d/ are executed before the init process
10796 enters the single user state. When switching to runlevel
1, the state
10797 is in fact not ending in runlevel
1, but it passes through runlevel
1
10798 and end up in the single user mode (see /etc/rc1.d/S03single, which
10799 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
10800 1. It is confusing that the
'S
' (single user) init mode is not the
10801 mode enabled by /etc/rcS.d/ (which is more like the initial boot
10804 <p
>This summary might make it clearer. When booting for the first
10805 time into single user mode, the following commands are executed:
10806 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
10807 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
10808 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
10809 trying to continue after visiting single user mode. Not all services
10810 are started again as they should, causing the machine to end up in an
10811 unpredicatble state. This is why Debian admins recommend rebooting
10812 after visiting single user mode.
</p
>
10814 <p
>A similar problem with runlevel
1 is caused by the amount of
10815 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
10816 to runlevel
1, the services started from /etc/rcS.d/ are not properly
10817 stopped when passing through the scripts in /etc/rc1.d/, and not
10818 started again when switching away from runlevel
1 to the runlevels
10819 2-
5. I believe the problem is best fixed by moving all the scripts
10820 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
10821 functioning single user mode during boot.
</p
>
10823 <p
>I have spent several years investigating the Debian boot system,
10824 and discovered this problem a few years ago. I suspect it originates
10825 from when sysvinit was introduced into Debian, a long time ago.
</p
>
10830 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
10831 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
10832 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
10833 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
10834 <description><p
>In the Debian boot system, several packages include scripts that
10835 are started from /etc/rcS.d/. In fact, there is a bite more of them
10836 than make sense, and this causes a few problems. What kind of
10837 problems, you might ask. There are at least two problems. The first
10838 is that it is not possible to recover a machine after switching to
10839 runlevel
1. One need to actually reboot to get the machine back to
10840 the expected state. The other is that single user boot will sometimes
10841 run into problems because some of the subsystems are activated before
10842 the root login is presented, causing problems when trying to recover a
10843 machine from a problem in that subsystem. A minor additional point is
10844 that moving more scripts out of rcS.d/ and into the other rc#.d/
10845 directories will increase the amount of scripts that can run in
10846 parallel during boot, and thus decrease the boot time.
</p
>
10848 <p
>So, which scripts should start from rcS.d/. In short, only the
10849 scripts that _have_ to execute before the root login prompt is
10850 presented during a single user boot should go there. Everything else
10851 should go into the numeric runlevels. This means things like
10852 lm-sensors, fuse and x11-common should not run from rcS.d, but from
10853 the numeric runlevels. Today in Debian, there are around
115 init.d
10854 scripts that are started from rcS.d/, and most of them should be moved
10855 out. Do your package have one of them? Please help us make single
10856 user and runlevel
1 better by moving it.
</p
>
10858 <p
>Scripts setting up the screen, keyboard, system partitions
10859 etc. should still be started from rcS.d/, but there is for example no
10860 need to have the network enabled before the single user login prompt
10861 is presented.
</p
>
10863 <p
>As always, things are not so easy to fix as they sound. To keep
10864 Debian systems working while scripts migrate and during upgrades, the
10865 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
10866 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
10867 and the next ones can only be moved when their dependencies have been
10868 moved first. This migration must be done sequentially while we ensure
10869 that the package system upgrade packages in the right order to keep
10870 the system state correct. This will require some coordination when it
10871 comes to network related packages, but most of the packages with
10872 scripts that should migrate do not have anything in rcS.d/ depending
10873 on them. Some packages have already been updated, like the sudo
10874 package, while others are still left to do. I wish I had time to work
10875 on this myself, but real live constrains make it unlikely that I will
10876 find time to push this forward.
</p
>
10881 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
10882 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
10883 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
10884 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
10885 <description><p
>While at Debconf11, I have several times during discussions
10886 mentioned the issues I believe should be improved in Debian for its
10887 desktop to be useful for more people. The use case for this is my
10888 parents, which are currently running Kubuntu which solve the
10891 <p
>I suspect these four missing features are not very hard to
10892 implement. After all, they are present in Ubuntu, so if we wanted to
10893 do this in Debian we would have a source.
</p
>
10897 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
10898 are new packages available for upgrades, a icon in the KDE status bar
10899 indicate this, and clicking on it will activate the simple upgrade
10900 tool to handle it. I have no problem guiding both of my parents
10901 through the process over the phone. If a kernel reboot is required,
10902 this too is indicated by the status bars and the upgrade tool. Last
10903 time I checked, nothing with the same features was working in KDE in
10906 <li
><strong
>Simple handling of missing Firefox browser
10907 plugins.
</strong
> When the browser encounter a MIME type it do not
10908 currently have a handler for, it will ask the user if the system
10909 should search for a package that would add support for this MIME type,
10910 and if the user say yes, the APT sources will be searched for packages
10911 advertising the MIME type in their control file (visible in the
10912 Packages file in the APT archive). If one or more packages are found,
10913 it is a simple click of the mouse to add support for the missing mime
10914 type. If the package require the user to accept some non-free
10915 license, this is explained to the user. The entire process make it
10916 more clear to the user why something do not work in the browser, and
10917 make the chances higher for the user to blame the web page authors and
10918 not the browser for any missing features.
</li
>
10920 <li
><strong
>Simple handling of missing multimedia codec/format
10921 handlers.
</strong
> When the media players encounter a format or codec
10922 it is not supporting, a dialog pop up asking the user if the system
10923 should search for a package that would add support for it. This
10924 happen with things like MP3, Windows Media or H
.264. The selection
10925 and installation procedure is very similar to the Firefox browser
10926 plugin handling. This is as far as I know implemented using a
10927 gstreamer hook. The end result is that the user easily get access to
10928 the codecs that are present from the APT archives available, while
10929 explaining more on why a given format is unsupported by Ubuntu.
</li
>
10931 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
10932 displaying a text/plain file in my Debian browser, it will propose to
10933 start emacs to show it. If I remember correctly, when doing the same
10934 in Kunbutu it show the file as a text file in the browser. At least I
10935 know Opera will show text files within the browser. I much prefer the
10936 latter behaviour.
</li
>
10940 <p
>There are other nice features as well, like the simplified suite
10941 upgrader, but given that I am the one mostly doing the dist-upgrade,
10942 it do not matter much.
</p
>
10944 <p
>I really hope we could get these features in place for the next
10945 Debian release. It would require the coordinated effort of several
10946 maintainers, but would make the end user experience a lot better.
</p
>
10951 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
10952 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
10953 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
10954 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
10955 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
10956 site is build on Debian/Squeeze, and this platform was chosen because
10957 I am most familiar with Debian (being a Debian Developer for around
10
10958 years) because it is the latest stable Debian release which should get
10959 security support for a few years.
</p
>
10961 <p
>The web service is written in Perl, and depend on some perl modules
10962 that are missing in Debian at the moment. It would be great if these
10963 modules were added to the Debian archive, allowing anyone to set up
10964 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
10965 in their own country using only Debian packages. The list of modules
10966 missing in Debian/Squeeze isn
't very long, and I hope the perl group
10967 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
10968 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
10969 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
10970 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
10971 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
10972 easier in the future.
</p
>
10974 <p
>Thanks to the great tools in Debian, getting the missing modules
10975 installed on my server was a simple call to
'cpan2deb Module::Name
'
10976 and
'dpkg -i
' to install the resulting package. But this leave me
10977 with the responsibility of tracking security problems, which I really
10978 do not have time for.
</p
>
10983 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
10984 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
10985 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
10986 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
10987 <description><p
>Here is a small update for my English readers. Most of my blog
10988 posts have been in Norwegian the last few weeks, so here is a short
10989 update in English.
</p
>
10991 <p
>The kids still keep me too busy to get much free software work
10992 done, but I did manage to organise a project to get a Norwegian port
10993 of the British service
10994 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
10995 and it has been running for a month now. The entire project has been
10996 organised by me and two others. Around Christmas we gathered sponsors
10997 to fund the development work. In January I drafted a contract with
10998 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
10999 and in February the development took place. Most of it involved
11000 converting the source to use GPS coordinates instead of British
11001 easting/northing, and the resulting code should be a lot easier to get
11002 running in any country by now. The Norwegian
11003 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
11004 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
11005 source and the source for administrative borders in Norway, and
11006 support for this had to be added/fixed.
</p
>
11008 <p
>The Norwegian version went live March
3th, and we spent the weekend
11009 polishing the system before we announced it March
7th. The system is
11010 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
11011 problem reports in a few weeks. Soon we hope to announce the Android
11012 and iPhone versions making it even easier to report problems with the
11013 public infrastructure.
</p
>
11015 <p
>Perhaps something to consider for those of you in countries without
11016 such service?
</p
>
11021 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
11022 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
11023 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
11024 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
11025 <description><p
>The last few days I have looked at ways to track open security
11026 issues here at my work with the University of Oslo. My idea is that
11027 it should be possible to use the information about security issues
11028 available on the Internet, and check our locally
11029 maintained/distributed software against this information. It should
11030 allow us to verify that no known security issues are forgotten. The
11031 CVE database listing vulnerabilities seem like a great central point,
11032 and by using the package lists from Debian mapped to CVEs provided by
11033 the testing security team, I believed it should be possible to figure
11034 out which security holes were present in our free software
11035 collection.
</p
>
11037 <p
>After reading up on the topic, it became obvious that the first
11038 building block is to be able to name software packages in a unique and
11039 consistent way across data sources. I considered several ways to do
11040 this, for example coming up with my own naming scheme like using URLs
11041 to project home pages or URLs to the Freshmeat entries, or using some
11042 existing naming scheme. And it seem like I am not the first one to
11043 come across this problem, as MITRE already proposed and implemented a
11044 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
11045 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
11046 software, hardware and other platform components. The CPE ids are
11047 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
11048 Vulnerability Database
</a
>, allowing me to look up know security
11049 issues for any CPE name. With this in place, all I need to do is to
11050 locate the CPE id for the software packages we use at the university.
11051 This is fairly trivial (I google for
'cve cpe $package
' and check the
11052 NVD entry if a CVE for the package exist).
</p
>
11054 <p
>To give you an example. The GNU gzip source package have the CPE
11055 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
11056 check out, one could look up
11057 <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
11058 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
11059 The most recent one is
11060 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
11061 and at the bottom of the NVD page for this vulnerability the complete
11062 list of affected versions is provided.
</p
>
11064 <p
>The NVD database of CVEs is also available as a XML dump, allowing
11065 for offline processing of issues. Using this dump, I
've written a
11066 small script taking a list of CPEs as input and list all CVEs
11067 affecting the packages represented by these CPEs. One give it CPEs
11068 with version numbers as specified above and get a list of open
11069 security issues out.
</p
>
11071 <p
>Of course for this approach to be useful, the quality of the NVD
11072 information need to be high. For that to happen, I believe as many as
11073 possible need to use and contribute to the NVD database. I notice
11075 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
11076 map from CVE to CPE
</a
>, indicating that they are using the CPE
11077 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
11079 <p
>To get an idea about the quality for free software, I spent some
11080 time making it possible to compare the CVE database from Debian with
11081 the CVE database in NVD. The result look fairly good, but there are
11082 some inconsistencies in NVD (same software package having several
11083 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
11084 Debian believe are affected by a CVE). Hope to find time to improve
11085 the quality of NVD, but that require being able to get in touch with
11086 someone maintaining it. So far my three emails with questions and
11087 corrections have not seen any reply, but I hope contact can be
11088 established soon.
</p
>
11090 <p
>An interesting application for CPEs is cross platform package
11091 mapping. It would be useful to know which packages in for example
11092 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
11093 this would be trivial if all linux distributions provided CPE entries
11094 for their packages.
</p
>
11099 <title>Which module is loaded for a given PCI and USB device?
</title>
11100 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
11101 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
11102 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
11103 <description><p
>In the
11104 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
11105 package in Debian, there is a script to report useful information
11106 about the running hardware for use when people report missing
11107 information. One part of this script that I find very useful when
11108 debugging hardware problems, is the part mapping loaded kernel module
11109 to the PCI device it claims. It allow me to quickly see if the kernel
11110 module I expect is driving the hardware I am struggling with. To see
11111 the output, make sure discover-data is installed and run
11112 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
11113 one of my machines like this:
</p
>
11117 10de:
03eb i2c_nforce2
11120 10de:
03f0 snd_hda_intel
11125 109e:
0878 snd_bt87x
11129 <p
>The code in question look like this, slightly modified for
11130 readability and to drop the output to file descriptor
3:
</p
>
11133 if [ -d /sys/bus/pci/devices/ ] ; then
11134 echo loaded pci modules:
11136 cd /sys/bus/pci/devices/
11137 for address in * ; do
11138 if [ -d
"$address/driver/module
" ] ; then
11139 module=`cd $address/driver/module ; pwd -P | xargs basename`
11140 if grep -q
"^$module
" /proc/modules ; then
11141 address=$(echo $address |sed s/
0000://)
11142 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
11143 echo
"$id $module
"
11152 <p
>Similar code could be used to extract USB device module
11153 mappings:
</p
>
11156 if [ -d /sys/bus/usb/devices/ ] ; then
11157 echo loaded usb modules:
11159 cd /sys/bus/usb/devices/
11160 for address in * ; do
11161 if [ -d
"$address/driver/module
" ] ; then
11162 module=`cd $address/driver/module ; pwd -P | xargs basename`
11163 if grep -q
"^$module
" /proc/modules ; then
11164 address=$(echo $address |sed s/
0000://)
11165 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
11166 if [
"$id
" ] ; then
11167 echo
"$id $module
"
11177 <p
>This might perhaps be something to include in other tools as
11183 <title>How to test if a laptop is working with Linux
</title>
11184 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
11185 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
11186 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
11187 <description><p
>The last few days I have spent at work here at the
<a
11188 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
11189 batch of computers will work with Linux. Every year for the last few
11190 years the university have organised shared bid of a few thousand
11191 computers, and this year HP won the bid. Two different desktops and
11192 five different laptops are on the list this year. We in the UNIX
11193 group want to know which one of these computers work well with RHEL
11194 and Ubuntu, the two Linux distributions we currently handle at the
11195 university.
</p
>
11197 <p
>My test method is simple, and I share it here to get feedback and
11198 perhaps inspire others to test hardware as well. To test, I PXE
11199 install the OS version of choice, and log in as my normal user and run
11200 a few applications and plug in selected pieces of hardware. When
11201 something fail, I make a note about this in the test matrix and move
11202 on. If I have some spare time I try to report the bug to the OS
11203 vendor, but as I only have the machines for a short time, I rarely
11204 have the time to do this for all the problems I find.
</p
>
11206 <p
>Anyway, to get to the point of this post. Here is the simple tests
11207 I perform on a new model.
</p
>
11211 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
11212 and Ubuntu Maverik at the moment. If I feel like it, I also test with
11213 RHEL5 and Debian Edu/Squeeze.
</li
>
11215 <li
>Is X.org working? If the graphical login screen show up after
11216 installation, X.org is working.
</li
>
11218 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
11219 package mesa-utils on Ubuntu) and writing down the frames per second
11220 reported by the program.
</li
>
11222 <li
>Is sound working? With Gnome and KDE, a sound is played when
11223 logging in, and if I can hear this the test is successful. If there
11224 are several audio exits on the machine, I try them all and check if
11225 the Gnome/KDE audio mixer can control where to send the sound. I
11226 normally test this by playing
11227 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
11228 video
</a
> in Firefox/Iceweasel.
</li
>
11230 <li
>Is the USB subsystem working? I test this by plugging in a USB
11231 memory stick and see if Gnome/KDE notices this.
</li
>
11233 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
11234 I have lying around, and see if Gnome/KDE notices this.
</li
>
11236 <li
>Is any built in camera working? Test using cheese, and see if a
11237 picture from the v4l device show up.
</li
>
11239 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
11240 any bluetooth devices are discovered. In my office, I normally see a
11243 <li
>For laptops, is the SD or Compaq Flash reader working. I have
11244 memory modules lying around, and stick them in and see if Gnome/KDE
11245 notice this.
</li
>
11247 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
11248 special button work, and if the laptop continue to work after
11251 <li
>For laptops, is the extra buttons working, like audio level,
11252 adjusting background light, switching on/off external video output,
11253 switching on/off wifi, bluetooth, etc? The set of buttons differ from
11254 laptop to laptop, so I just write down which are working and which are
11257 <li
>Some laptops have smart card readers, finger print readers,
11258 acceleration sensors etc. I rarely test these, as I do not know how
11259 to quickly test if they are working or not, so I only document their
11260 existence.
</li
>
11264 <p
>By now I suspect you are really curious what the test results are
11265 for the HP machines I am testing. I
'm not done yet, so I will report
11266 the test results later. For now I can report that HP
8100 Elite work
11267 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
11268 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
11269 can see, I have most machines left to test. One interesting
11270 observation is that Ubuntu Lucid has almost twice the frame rate than
11271 RHEL6 with glxgears. No idea why.
</p
>
11276 <title>Some thoughts on BitCoins
</title>
11277 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
11278 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
11279 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
11280 <description><p
>As I continue to explore
11281 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
11282 what properties the system have, and how it will be affected by laws
11283 and regulations here in Norway. Here are some random notes.
</p
>
11285 <p
>One interesting thing to note is that since the transactions are
11286 verified using a peer to peer network, all details about a transaction
11287 is known to everyone. This means that if a BitCoin address has been
11288 published like I did with mine in my initial post about BitCoin, it is
11289 possible for everyone to see how many BitCoins have been transfered to
11290 that address. There is even a web service to look at the details for
11291 all transactions. There I can see that my address
11292 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
11293 have received
16.06 Bitcoin, the
11294 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
11295 address of Simon Phipps have received
181.97 BitCoin and the address
11296 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
11297 of EFF have received
2447.38 BitCoins so far. Thank you to each and
11298 every one of you that donated bitcoins to support my activity. The
11299 fact that anyone can see how much money was transfered to a given
11300 address make it more obvious why the BitCoin community recommend to
11301 generate and hand out a new address for each transaction. I
'm told
11302 there is no way to track which addresses belong to a given person or
11303 organisation without the person or organisation revealing it
11304 themselves, as Simon, EFF and I have done.
</p
>
11306 <p
>In Norway, and in most other countries, there are laws and
11307 regulations limiting how much money one can transfer across the border
11308 without declaring it. There are money laundering, tax and accounting
11309 laws and regulations I would expect to apply to the use of BitCoin.
11310 If the Skolelinux foundation
11311 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
11312 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
11313 normal bank transfers like EFF is doing, how should this be accounted?
11314 Given that it is impossible to know if money can cross the border or
11315 not, should everything or nothing be declared? What exchange rate
11316 should be used when calculating taxes? Would receivers have to pay
11317 income tax if the foundation were to pay Skolelinux contributors in
11318 BitCoin? I have no idea, but it would be interesting to know.
</p
>
11320 <p
>For a currency to be useful and successful, it must be trusted and
11321 accepted by a lot of users. It must be possible to get easy access to
11322 the currency (as a wage or using currency exchanges), and it must be
11323 easy to spend it. At the moment BitCoin seem fairly easy to get
11324 access to, but there are very few places to spend it. I am not really
11325 a regular user of any of the vendor types currently accepting BitCoin,
11326 so I wonder when my kind of shop would start accepting BitCoins. I
11327 would like to buy electronics, travels and subway tickets, not herbs
11328 and books. :) The currency is young, and this will improve over time
11329 if it become popular, but I suspect regular banks will start to lobby
11330 to get BitCoin declared illegal if it become popular. I
'm sure they
11331 will claim it is helping fund terrorism and money laundering (which
11332 probably would be true, as is any currency in existence), but I
11333 believe the problems should be solved elsewhere and not by blaming
11334 currencies.
</p
>
11336 <p
>The process of creating new BitCoins is called mining, and it is
11337 CPU intensive process that depend on a bit of luck as well (as one is
11338 competing against all the other miners currently spending CPU cycles
11339 to see which one get the next lump of cash). The
"winner
" get
50
11340 BitCoin when this happen. Yesterday I came across the obvious way to
11341 join forces to increase ones changes of getting at least some coins,
11342 by coordinating the work on mining BitCoins across several machines
11343 and people, and sharing the result if one is lucky and get the
50
11344 BitCoins. Check out
11345 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
11346 if this sounds interesting. I have not had time to try to set up a
11347 machine to participate there yet, but have seen that running on ones
11348 own for a few days have not yield any BitCoins througth mining
11351 <p
>Update
2010-
12-
15: Found an
<a
11352 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
11353 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
11354 it was interesting to read. The arguments presented seem to be
11355 equally valid for gold, which was used as a currency for many years.
</p
>
11360 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
11361 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
11362 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
11363 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
11364 <description><p
>With this weeks lawless
11365 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
11366 attacks
</a
> on Wikileak and
11367 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
11368 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
11369 not be trusted to handle money transactions.
11371 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
11372 Phipps on bitcoin
</a
> reminded me about a project that a friend of
11373 mine mentioned earlier. I decided to follow Simon
's example, and get
11374 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
11375 some help from my friend to get it all running, and he even handed me
11376 some bitcoins to get started. I even donated a few bitcoins to Simon
11377 for helping me remember BitCoin.
</p
>
11379 <p
>So, what is bitcoins, you probably wonder? It is a digital
11380 crypto-currency, decentralised and handled using peer-to-peer
11381 networks. It allows anonymous transactions and prohibits central
11382 control over the transactions, making it impossible for governments
11383 and companies alike to block donations and other transactions. The
11384 source is free software, and while the key dependency wxWidgets
2.9
11385 for the graphical user interface is missing in Debian, the command
11386 line client builds just fine. Hopefully Jonas
11387 <a href=
"http://bugs.debian.org/
578157">will get the package into
11388 Debian
</a
> soon.
</p
>
11390 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
11391 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
11392 bitcoins
</a
> when selling services and goods, and there are even
11393 currency
"stock
" markets where the exchange rate is decided. There
11394 are not many users so far, but the concept seems promising. If you
11395 want to get started and lack a friend with any bitcoins to spare,
11397 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
11398 bitcoin at the time of writing). Use
11399 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
11400 on the current exchange rates.
</p
>
11402 <p
>As an experiment, I have decided to set up bitcoind on one of my
11403 machines. If you want to support my activity, please send Bitcoin
11404 donations to the address
11405 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
11410 <title>Why isn
't Debian Edu using VLC?
</title>
11411 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
11412 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
11413 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
11414 <description><p
>In the latest issue of Linux Journal, the readers choices were
11415 presented, and the winner among the multimedia player were VLC.
11416 Personally, I like VLC, and it is my player of choice when I first try
11417 to play a video file or stream. Only if VLC fail will I drag out
11418 gmplayer to see if it can do better. The reason is mostly the failure
11419 model and trust. When VLC fail, it normally pop up a error message
11420 reporting the problem. When mplayer fail, it normally segfault or
11421 just hangs. The latter failure mode drain my trust in the program.
<p
>
11423 <p
>But even if VLC is my player of choice, we have choosen to use
11424 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
11425 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
11426 plugin to play web videos seamlessly, and the VLC browser plugin is
11427 not very good. For example, it lack in-line control buttons, so there
11428 is no way for the user to pause the video. Also, when I
11429 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
11430 tested the browser plugins
</a
> available in Debian, the VLC plugin
11431 failed on several video pages where mplayer based plugins worked. If
11432 the browser plugin for VLC was as good as the gecko-mediaplayer
11433 package (which uses mplayer), we would switch.
</P
>
11435 <p
>While VLC is a good player, its user interface is slightly
11436 annoying. The most annoying feature is its inconsistent use of
11437 keyboard shortcuts. When the player is in full screen mode, its
11438 shortcuts are different from when it is playing the video in a window.
11439 For example, space only work as pause when in full screen mode. I
11440 wish it had consisten shortcuts and that space also would work when in
11441 window mode. Another nice shortcut in gmplayer is [enter] to restart
11442 the current video. It is very nice when playing short videos from the
11443 web and want to restart it when new people arrive to have a look at
11444 what is going on.
</p
>
11449 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
11450 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
11451 <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>
11452 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
11453 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
11454 upgrade testing of the
11455 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
11456 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
11457 This seem like a very good idea, so I adjusted by test scripts and
11458 can now present the updated result from today:
</p
>
11460 <p
>This is for Gnome:
</p
>
11462 <p
>Installed using apt-get, missing with aptitude
</p
>
11464 <blockquote
><p
>
11469 browser-plugin-gnash
11476 freedesktop-sound-theme
11478 gconf-defaults-service
11491 gnome-codec-install
11493 gnome-desktop-environment
11497 gnome-session-canberra
11499 gnome-themes-extras
11502 gstreamer0.10-fluendo-mp3
11503 gstreamer0.10-tools
11505 gtk2-engines-pixbuf
11506 gtk2-engines-smooth
11508 libapache2-mod-dnssd
11511 libaprutil1-dbd-sqlite3
11514 libboost-date-time1.42
.0
11515 libboost-python1.42
.0
11516 libboost-thread1.42
.0
11518 libchamplain-gtk-
0.4-
0
11520 libclutter-gtk-
0.10-
0
11527 libfreerdp-plugins-standard
11540 libgnome-vfs2.0-cil
11542 libgnomepanel2.24-cil
11547 libgtksourceview2.0-common
11548 libmono-addins-gui0.2-cil
11549 libmono-addins0.2-cil
11550 libmono-cairo2.0-cil
11551 libmono-corlib2.0-cil
11552 libmono-i18n-west2.0-cil
11553 libmono-posix2.0-cil
11554 libmono-security2.0-cil
11555 libmono-sharpzip2.84-cil
11556 libmono-system2.0-cil
11559 libndesk-dbus-glib1.0-cil
11560 libndesk-dbus1.0-cil
11570 libtelepathy-farsight0
11579 nautilus-sendto-empathy
11583 python-aptdaemon-gtk
11585 python-beautifulsoup
11600 python-gtksourceview2
11611 python-pkg-resources
11618 python-twisted-conch
11619 python-twisted-core
11624 python-zope.interface
11626 remmina-plugin-data
11629 rhythmbox-plugin-cdrecorder
11636 system-config-printer-udev
11638 telepathy-mission-control-
5
11645 transmission-common
11649 </p
></blockquote
>
11651 <p
>Installed using apt-get, removed with aptitude
</p
>
11653 <blockquote
><p
>
11657 epiphany-extensions
11659 fast-user-switch-applet
11678 libgtksourceview2.0-
0
11680 libsdl1.2debian-alsa
11686 system-config-printer
11691 </p
></blockquote
>
11693 <p
>Installed using aptitude, missing with apt-get
</p
>
11695 <blockquote
><p
>
11696 gstreamer0.10-gnomevfs
11697 </p
></blockquote
>
11699 <p
>Installed using aptitude, removed with apt-get
</p
>
11701 <blockquote
><p
>
11703 </p
></blockquote
>
11705 <p
>This is for KDE:
</p
>
11707 <p
>Installed using apt-get, missing with aptitude
</p
>
11709 <blockquote
><p
>
11711 </p
></blockquote
>
11713 <p
>Installed using apt-get, removed with aptitude
</p
>
11715 <blockquote
><p
>
11717 network-manager-kde
11718 </p
></blockquote
>
11720 <p
>Installed using aptitude, missing with apt-get
</p
>
11722 <blockquote
><p
>
11736 kdeartwork-emoticons
11738 kdeartwork-theme-icon
11742 kdebase-workspace-bin
11743 kdebase-workspace-data
11755 konqueror-nsplugins
11757 kscreensaver-xsavers
11772 plasma-dataengines-workspace
11774 plasma-desktopthemes-artwork
11775 plasma-runners-addons
11776 plasma-scriptengine-googlegadgets
11777 plasma-scriptengine-python
11778 plasma-scriptengine-qedje
11779 plasma-scriptengine-ruby
11780 plasma-scriptengine-webkit
11781 plasma-scriptengines
11782 plasma-wallpapers-addons
11783 plasma-widget-folderview
11784 plasma-widget-networkmanagement
11787 update-notifier-kde
11788 xscreensaver-data-extra
11790 xscreensaver-gl-extra
11791 xscreensaver-screensaver-bsod
11792 </p
></blockquote
>
11794 <p
>Installed using aptitude, removed with apt-get
</p
>
11796 <blockquote
><p
>
11798 google-gadgets-common
11816 libggadget-qt-
1.0-
0b
11821 libkonqsidebarplugin4a
11825 libkunitconversion4
11830 libplasma-geolocation-interface4
11832 libplasmagenericshell4
11846 libsmokeknewstuff2-
3
11847 libsmokeknewstuff3-
3
11849 libsmokektexteditor3
11857 libsmokeqtnetwork4-
3
11858 libsmokeqtopengl4-
3
11859 libsmokeqtscript4-
3
11863 libsmokeqtuitools4-
3
11864 libsmokeqtwebkit4-
3
11875 plasma-dataengines-addons
11876 plasma-scriptengine-superkaramba
11877 plasma-widget-lancelot
11878 plasma-widgets-addons
11879 plasma-widgets-workspace
11883 update-notifier-common
11884 </p
></blockquote
>
11886 <p
>Running apt-get autoremove made the results using apt-get and
11887 aptitude a bit more similar, but there are still quite a lott of
11888 differences. I have no idea what packages should be installed after
11889 the upgrade, but hope those that do can have a look.
</p
>
11894 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
11895 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
11896 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
11897 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
11898 <description><p
>Most of the computers in use by the
11899 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
11900 are virtual machines. And they have been Xen machines running on a
11901 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
11902 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
11903 bit harder that it could have been, because we set up the Xen virtual
11904 machines to get the virtual partitions from LVM, which as far as I
11905 know is not supported by KVM. So to migrate, we had to convert
11906 several LVM logical volumes to partitions on a virtual disk file.
</p
>
11909 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
11910 nice recipe
</a
> to do this, and wrote the following script to do the
11911 migration. It uses qemu-img from the qemu package to make the disk
11912 image, parted to partition it, losetup and kpartx to present the disk
11913 image partions as devices, and dd to copy the data. I NFS mounted the
11914 new servers storage area on the old server to do the migration.
</p
>
11920 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
11925 if [ -z
"$
1" ] ; then
11926 echo
"Usage: $
0 &lt;hostname
&gt;
"
11929 host=
"$
1"
11932 if [ ! -e /dev/vg_data/$host-disk ] ; then
11933 echo
"error: unable to find LVM volume for $host
"
11937 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
11938 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11939 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11940 totalsize=$(( ( $disksize + $swapsize ) ))
11943 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
11944 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
11946 parted $img mklabel msdos
11947 parted $img mkpart primary linux-swap
0 $disksize
11948 parted $img mkpart primary ext2 $disksize $totalsize
11949 parted $img set
1 boot on
11952 losetup /dev/loop0 $img
11953 kpartx -a /dev/loop0
11955 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
11956 fsck.ext3 -f /dev/mapper/loop0p1 || true
11957 mkswap /dev/mapper/loop0p2
11959 kpartx -d /dev/loop0
11960 losetup -d /dev/loop0
11963 <p
>The script is perhaps so simple that it is not copyrightable, but
11964 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
11966 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
11967 the new disk image attached, installed grub-pc and linux-image-
686 and
11968 set up grub to boot from the disk image. After this, the KVM machines
11969 seem to work just fine.
</p
>
11974 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
11975 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
11976 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
11977 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
11978 <description><p
>I
'm still running upgrade testing of the
11979 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
11980 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
11981 status. Here is a short update based on a test I ran
20101118.
</p
>
11983 <p
>I still do not know what a correct migration should look like, so I
11984 report any differences between apt and aptitude and hope someone else
11985 can see if anything should be changed.
</p
>
11987 <p
>This is for Gnome:
</p
>
11989 <p
>Installed using apt-get, missing with aptitude
</p
>
11991 <blockquote
><p
>
11992 apache2.2-bin aptdaemon at-spi baobab binfmt-support
11993 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
11994 dmz-cursor-theme empathy empathy-common finger
11995 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
11996 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11997 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11998 gnome-cards-data gnome-codec-install gnome-core
11999 gnome-desktop-environment gnome-disk-utility gnome-screenshot
12000 gnome-search-tool gnome-session-canberra gnome-spell
12001 gnome-system-log gnome-themes-extras gnome-themes-more
12002 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
12003 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
12004 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
12005 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
12006 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
12007 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
12008 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
12009 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
12010 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
12011 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
12012 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
12013 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
12014 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
12015 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
12016 libgtk2.0-cil libgtkglext1 libgtksourceview-common
12017 libgtksourceview2.0-common libmono-addins-gui0.2-cil
12018 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
12019 libmono-i18n-west2.0-cil libmono-posix2.0-cil
12020 libmono-security2.0-cil libmono-sharpzip2.84-cil
12021 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
12022 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
12023 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
12024 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
12025 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
12026 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
12027 libxalan2-java libxerces2-java media-player-info mesa-utils
12028 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
12029 nautilus-sendto-empathy openoffice.org-writer2latex
12030 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
12031 python-aptdaemon python-aptdaemon-gtk python-axiom
12032 python-beautifulsoup python-bugbuddy python-clientform
12033 python-coherence python-configobj python-crypto python-cupshelpers
12034 python-cupsutils python-eggtrayicon python-elementtree
12035 python-epsilon python-evolution python-feedparser python-gdata
12036 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
12037 python-gtksourceview2 python-httplib2 python-louie python-mako
12038 python-markupsafe python-mechanize python-nevow python-notify
12039 python-opengl python-openssl python-pam python-pkg-resources
12040 python-pyasn1 python-pysqlite2 python-rdflib python-serial
12041 python-tagpy python-twisted-bin python-twisted-conch
12042 python-twisted-core python-twisted-web python-utidylib python-webkit
12043 python-xdg python-zope.interface remmina remmina-plugin-data
12044 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
12045 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
12046 software-center svgalibg1 system-config-printer-udev
12047 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
12048 totem totem-coherence totem-mozilla totem-plugins
12049 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
12051 </p
></blockquote
>
12053 Installed using apt-get, removed with aptitude
12055 <blockquote
><p
>
12056 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
12057 epiphany-extensions epiphany-gecko evolution-exchange
12058 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
12059 gedit-common gnome-app-install gnome-games gnome-games-data
12060 gnome-nettool gnome-system-tools gnome-themes gnome-utils
12061 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
12062 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
12063 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
12064 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
12065 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
12066 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
12067 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
12068 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
12069 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
12070 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
12071 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
12072 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
12073 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
12074 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
12075 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
12076 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
12077 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
12078 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
12079 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
12080 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
12081 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
12082 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
12083 sound-juicer swfdec-gnome system-config-printer totem-common
12084 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
12085 </p
></blockquote
>
12087 <p
>Installed using aptitude, missing with apt-get
</p
>
12089 <blockquote
><p
>
12090 gstreamer0.10-gnomevfs
12091 </p
></blockquote
>
12093 <p
>Installed using aptitude, removed with apt-get
</p
>
12095 <blockquote
><p
>
12097 </p
></blockquote
>
12099 <p
>This is for KDE:
</p
>
12101 <p
>Installed using apt-get, missing with aptitude
</p
>
12103 <blockquote
><p
>
12104 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
12105 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
12106 ghostscript-x git gnome-audio gnugo granatier gs-common
12107 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
12108 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
12109 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
12110 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12111 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
12112 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
12113 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12114 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
12115 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
12116 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
12117 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
12118 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
12119 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
12120 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
12121 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
12122 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
12123 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
12124 libkrossui4 libmailtools-perl libmime-tools-perl
12125 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
12126 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
12127 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
12128 lirc luatex marble networkstatus noatun-plugins
12129 openoffice.org-writer2latex palapeli palapeli-data parley
12130 parley-data poster psutils pulseaudio pulseaudio-esound-compat
12131 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
12132 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
12133 ttf-sazanami-gothic
12134 </p
></blockquote
>
12136 <p
>Installed using apt-get, removed with aptitude
</p
>
12138 <blockquote
><p
>
12139 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
12140 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
12141 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
12142 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
12143 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
12144 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
12145 kitchensync kiten kjumpingcube klatin klettres klickety klines
12146 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
12147 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
12148 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
12149 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
12150 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
12151 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
12152 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
12153 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
12154 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12155 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
12156 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
12157 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12158 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
12159 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
12160 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
12161 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
12162 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12163 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
12164 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
12165 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
12166 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
12167 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
12168 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
12169 mpeglib network-manager-kde noatun pmount tex-common texlive-base
12170 texlive-common texlive-doc-base texlive-fonts-recommended tidy
12171 ttf-dustin ttf-kochi-gothic ttf-sjfonts
12172 </p
></blockquote
>
12174 <p
>Installed using aptitude, missing with apt-get
</p
>
12176 <blockquote
><p
>
12177 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
12178 kdeartwork kdebase kdebase-apps kdebase-workspace
12179 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
12180 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
12181 netpbm plasma-widget-folderview plasma-widget-networkmanagement
12182 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
12183 xscreensaver-screensaver-bsod
12184 </p
></blockquote
>
12186 <p
>Installed using aptitude, removed with apt-get
</p
>
12188 <blockquote
><p
>
12189 kdebase-bin konq-plugins konqueror
12190 </p
></blockquote
>
12195 <title>Gnash buildbot slave and Debian kfreebsd
</title>
12196 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
12197 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
12198 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
12199 <description><p
>Answering
12200 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
12201 call from the Gnash project
</a
> for
12202 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
12203 current source, I have set up a virtual KVM machine on the Debian
12204 Edu/Skolelinux virtualization host to test the git source on
12205 Debian/Squeeze. I hope this can help the developers in getting new
12206 releases out more often.
</p
>
12208 <p
>As the developers want less main-stream build platforms tested to,
12209 I have considered setting up a
<a
12210 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
12211 machine as well. I have also considered using the kfreebsd
12212 architecture in Debian as a file server in NUUG to get access to the
5
12213 TB zfs volume we currently use to store DV video. Because of this, I
12214 finally got around to do a test installation of Debian/Squeeze with
12215 kfreebsd. Installation went fairly smooth, thought I noticed some
12216 visual glitches in the cdebconf dialogs (black cursor left on the
12217 screen at random locations). Have not gotten very far with the
12218 testing. Noticed cfdisk did not work, but fdisk did so it was not a
12219 fatal problem. Have to spend some more time on it to see if it is
12220 useful as a file server for NUUG. Will try to find time to set up a
12221 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
12226 <title>Debian in
3D
</title>
12227 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
12228 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
12229 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
12230 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
12232 <p
>3D printing is just great. I just came across this Debian logo in
12234 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
12235 thingiverse blog
</a
>.
</p
>
12240 <title>Software updates
2010-
10-
24</title>
12241 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
12242 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
12243 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
12244 <description><p
>Some updates.
</p
>
12246 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
12247 raise money for the project is going well. The lower limit of
10
12248 signers was reached in
24 hours, and so far
13 people have signed it.
12249 More signers and more funding is most welcome, and I am really curious
12250 how far we can get before the time limit of December
24 is reached.
12253 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
12254 about what appear to be a great code coverage tool capable of
12255 generating code coverage stats without any changes to the source code.
12257 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
12258 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
12259 It is missing in Debian, but the git source built just fine in Squeeze
12260 after I installed libelf-dev, libdwarf-dev, pkg-config and
12261 libglib2.0-dev. Failed to build in Lenny, but suspect that is
12262 solvable. I hope kcov make it into Debian soon.
</p
>
12264 <p
>Finally found time to wrap up the release notes for
<a
12265 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
12266 new alpha release of Debian Edu
</a
>, and just published the second
12267 alpha test release of the Squeeze based Debian Edu /
12268 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
12269 release. Give it a try if you need a complete linux solution for your
12270 school, including central infrastructure server, workstations, thin
12271 client servers and diskless workstations. A nice touch added
12272 yesterday is RDP support on the thin client servers, for windows
12273 clients to get a Linux desktop on request.
</p
>
12278 <title>Some notes on Flash in Debian and Debian Edu
</title>
12279 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
12280 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
12281 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
12282 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
12283 popularity-contest numbers
</a
>, the adobe-flashplugin package the
12284 second most popular used package that is missing in Debian. The sixth
12285 most popular is flashplayer-mozilla. This is a clear indication that
12286 working flash is important for Debian users. Around
10 percent of the
12287 users submitting data to popcon.debian.org have this package
12288 installed.
</p
>
12290 <p
>In the report written by Lars Risan in August
2008
12291 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
12292 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
12293 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
12294 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
12295 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
12296 web sites require Flash to work, and lacking working Flash support in
12297 the web browser and the problems with installing it was perceived as a
12298 good reason to stay with Windows.
</p
>
12300 <p
>I once saw a funny and sad comment in a web forum, where Linux was
12301 said to be the retarded cousin that did not really understand
12302 everything you told him but could work fairly well. This was a
12303 comment regarding the problems Linux have with proprietary formats and
12304 non-standard web pages, and is sad because it exposes a fairly common
12305 understanding of whose fault it is if web pages that only work in for
12306 example Internet Explorer
6 fail to work on Firefox, and funny because
12307 it explain very well how annoying it is for users when Linux
12308 distributions do not work with the documents they receive or the web
12309 pages they want to visit.
</p
>
12311 <p
>This is part of the reason why I believe it is important for Debian
12312 and Debian Edu to have a well working Flash implementation in the
12313 distribution, to get at least popular sites as Youtube and Google
12314 Video to working out of the box. For Squeeze, Debian have the chance
12315 to include the latest version of Gnash that will make this happen, as
12316 the new release
0.8.8 was published a few weeks ago and is resting in
12317 unstable. The new version work with more sites that version
0.8.7.
12318 The Gnash maintainers have asked for a freeze exception, but the
12319 release team have not had time to reply to it yet. I hope they agree
12320 with me that Flash is important for the Debian desktop users, and thus
12321 accept the new package into Squeeze.
</p
>
12326 <title>Circular package dependencies harms apt recovery
</title>
12327 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
12328 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
12329 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
12330 <description><p
>I discovered this while doing
12331 <a href=
"https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
12332 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
12333 in Debian still got circular dependencies, and it is often claimed
12334 that apt and aptitude should be able to handle this just fine, but
12335 some times these dependency loops causes apt to fail.
</p
>
12337 <p
>An example is from todays
12338 <a href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
12339 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
12340 causes perl-modules to fail to upgrade. The cause is simple. If a
12341 package fail to unpack, then only part of packages with the circular
12342 dependency might end up being unpacked when unpacking aborts, and the
12343 ones already unpacked will fail to configure in the recovery phase
12344 because its dependencies are unavailable.
</p
>
12346 <p
>In this log, the problem manifest itself with this error:
</p
>
12348 <blockquote
><pre
>
12349 dpkg: dependency problems prevent configuration of perl-modules:
12350 perl-modules depends on perl (
>=
5.10.1-
1); however:
12351 Version of perl on system is
5.10.0-
19lenny
2.
12352 dpkg: error processing perl-modules (--configure):
12353 dependency problems - leaving unconfigured
12354 </pre
></blockquote
>
12356 <p
>The perl/perl-modules circular dependency is already
12357 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
12358 hopefully be solved as soon as possible, but it is not the only one,
12359 and each one of these loops in the dependency tree can cause similar
12360 failures. Of course, they only occur when there are bugs in other
12361 packages causing the unpacking to fail, but it is rather nasty when
12362 the failure of one package causes the problem to become worse because
12363 of dependency loops.
</p
>
12366 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
12367 tireless effort by Bill Allombert
</a
>, the number of circular
12369 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
12370 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
12372 <p
>Todays testing also exposed a bug in
12373 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
12374 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
12375 apt-get and aptitude, the latter possibly caused by some circular
12376 dependency. Reported both to BTS to try to get someone to look at
12382 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
12383 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
12384 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
12385 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
12386 <description><p
>This is a
12387 <a href=
"https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
12389 <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
12391 <a href=
"https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
12392 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
12394 <p
>As a step to try to see if it possible to merge the DNS and DHCP
12395 LDAP objects, I have had a look at how the packages pdns-backend-ldap
12396 and dhcp3-server-ldap in Debian use the LDAP server. The two
12397 implementations are quite different in how they use LDAP.
</p
>
12399 To get this information, I started slapd with debugging enabled and
12400 dumped the debug output to a file to get the LDAP searches performed
12401 on a Debian Edu main-server. Here is a summary.
12403 <p
><strong
>powerdns
</strong
></p
>
12405 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
12406 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
12409 <p
>PowerDNS have two modes of operation using LDAP as its backend.
12410 One
"strict
" mode where the forward and reverse DNS lookups are done
12411 using the same LDAP objects, and a
"tree
" mode where the forward and
12412 reverse entries are in two different subtrees in LDAP with a structure
12413 based on the DNS names, as in tjener.intern and
12414 2.2.0.10.in-addr.arpa.
</p
>
12416 <p
>In tree mode, the server is set up to use a LDAP subtree as its
12417 base, and uses a
"base
" scoped search for the DNS name by adding
12418 "dc=tjener,dc=intern,
" to the base with a filter for
12419 "(associateddomain=tjener.intern)
" for the forward entry and
12420 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
12421 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
12422 forward entries, it is looking for attributes named dnsttl, arecord,
12423 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
12424 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
12425 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
12426 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
12427 spfrecord and modifytimestamp. For reverse entries it is looking for
12428 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
12429 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
12430 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
12431 ldapsearch commands could look like this:
</p
>
12433 <blockquote
><pre
>
12434 ldapsearch -h ldap \
12435 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
12436 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
12437 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
12438 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
12439 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
12440 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
12442 ldapsearch -h ldap \
12443 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
12444 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
12445 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
12446 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
12447 srvrecord naptrrecord modifytimestamp
12448 </pre
></blockquote
>
12450 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
12451 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
12452 example LDAP objects used there. In addition to these objects, the
12453 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
12454 also exist.
</p
>
12456 <blockquote
><pre
>
12457 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
12459 objectclass: dnsdomain
12460 objectclass: domainrelatedobject
12463 associateddomain: tjener.intern
12465 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
12467 objectclass: dnsdomain2
12468 objectclass: domainrelatedobject
12470 ptrrecord: tjener.intern
12471 associateddomain:
2.2.0.10.in-addr.arpa
12472 </pre
></blockquote
>
12474 <p
>In strict mode, the server behaves differently. When looking for
12475 forward DNS entries, it is doing a
"subtree
" scoped search with the
12476 same base as in the tree mode for a object with filter
12477 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
12478 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
12479 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
12480 naptrrecord and modifytimestamp. For reverse entires it also do a
12481 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
12482 and the requested attributes are associateddomain, dnsttl and
12483 modifytimestamp. In short, in strict mode the objects with ptrrecord
12484 go away, and the arecord attribute in the forward object is used
12487 <p
>The forward and reverse searches can be simulated using ldapsearch
12488 like this:
</p
>
12490 <blockquote
><pre
>
12491 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
12492 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
12493 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
12494 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
12495 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
12496 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
12498 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
12499 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
12500 </pre
></blockquote
>
12502 <p
>In addition to the forward and reverse searches , there is also a
12503 search for SOA records, which behave similar to the forward and
12504 reverse lookups.
</p
>
12506 <p
>A thing to note with the PowerDNS behaviour is that it do not
12507 specify any objectclass names, and instead look for the attributes it
12508 need to generate a DNS reply. This make it able to work with any
12509 objectclass that provide the needed attributes.
</p
>
12511 <p
>The attributes are normally provided in the cosine (RFC
1274) and
12512 dnsdomain2 schemas. The latter is used for reverse entries like
12513 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
12515 <p
>In Debian Edu, we have created DNS objects using the object classes
12516 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
12517 attributes) and domainrelatedobject (for associatedDomain). The use
12518 of structural object classes make it impossible to combine these
12519 classes with the object classes used by DHCP.
</p
>
12521 <p
>There are other schemas that could be used too, for example the
12522 dnszone structural object class used by Gosa and bind-sdb for the DNS
12523 attributes combined with the domainrelatedobject object class, but in
12524 this case some unused attributes would have to be included as well
12525 (zonename and relativedomainname).
</p
>
12527 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
12528 mode and not use any of the existing objectclasses (dnsdomain,
12529 dnsdomain2 and dnszone) when one want to combine the DNS information
12530 with DHCP information, and instead create a auxiliary object class
12531 defined something like this (using the attributes defined for
12532 dnsdomain and dnsdomain2 or dnszone):
</p
>
12534 <blockquote
><pre
>
12535 objectclass ( some-oid NAME
'dnsDomainAux
'
12538 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
12539 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
12540 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
12541 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
12542 A6Record $ DNAMERecord
12544 </pre
></blockquote
>
12546 <p
>This will allow any object to become a DNS entry when combined with
12547 the domainrelatedobject object class, and allow any entity to include
12548 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
12549 developers asking for their view on this schema and if they are
12550 interested in providing such schema with PowerDNS, and I hope my
12551 message will be accepted into their mailing list soon.
</p
>
12553 <p
><strong
>ISC dhcp
</strong
></p
>
12555 <p
>The DHCP server searches for specific objectclass and requests all
12556 the object attributes, and then uses the attributes it want. This
12557 make it harder to figure out exactly what attributes are used, but
12558 thanks to the working example in Debian Edu I can at least get an idea
12559 what is needed without having to read the source code.
</p
>
12561 <p
>In the DHCP server configuration, the LDAP base to use and the
12562 search filter to use to locate the correct dhcpServer entity is
12563 stored. These are the relevant entries from
12564 /etc/dhcp3/dhcpd.conf:
</p
>
12566 <blockquote
><pre
>
12567 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
12568 ldap-dhcp-server-cn
"dhcp
";
12569 </pre
></blockquote
>
12571 <p
>The DHCP server uses this information to nest all the DHCP
12572 configuration it need. The cn
"dhcp
" is located using the given LDAP
12573 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
12574 search result is this entry:
</p
>
12576 <blockquote
><pre
>
12577 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
12580 objectClass: dhcpServer
12581 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12582 </pre
></blockquote
>
12584 <p
>The content of the dhcpServiceDN attribute is next used to locate the
12585 subtree with DHCP configuration. The DHCP configuration subtree base
12586 is located using a base scope search with base
"cn=DHCP
12587 Config,dc=skole,dc=skolelinux,dc=no
" and filter
12588 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
12589 The search result is this entry:
</p
>
12591 <blockquote
><pre
>
12592 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12595 objectClass: dhcpService
12596 objectClass: dhcpOptions
12597 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
12598 dhcpStatements: ddns-update-style none
12599 dhcpStatements: authoritative
12600 dhcpOption: smtp-server code
69 = array of ip-address
12601 dhcpOption: www-server code
72 = array of ip-address
12602 dhcpOption: wpad-url code
252 = text
12603 </pre
></blockquote
>
12605 <p
>Next, the entire subtree is processed, one level at the time. When
12606 all the DHCP configuration is loaded, it is ready to receive requests.
12607 The subtree in Debian Edu contain objects with object classes
12608 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
12609 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
12610 and information about netmasks, dynamic range etc. Leaving out the
12611 details here because it is not relevant for the focus of my
12612 investigation, which is to see if it is possible to merge dns and dhcp
12613 related computer objects.
</p
>
12615 <p
>When a DHCP request come in, LDAP is searched for the MAC address
12616 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
12617 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
12618 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
12619 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
12622 <blockquote
><pre
>
12623 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12626 objectClass: dhcpHost
12627 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
12628 dhcpStatements: fixed-address hostname
12629 </pre
></blockquote
>
12631 <p
>There is less flexiblity in the way LDAP searches are done here.
12632 The object classes need to have fixed names, and the configuration
12633 need to be stored in a fairly specific LDAP structure. On the
12634 positive side, the invidiual dhcpHost entires can be anywhere without
12635 the DN pointed to by the dhcpServer entries. The latter should make
12636 it possible to group all host entries in a subtree next to the
12637 configuration entries, and this subtree can also be shared with the
12638 DNS server if the schema proposed above is combined with the dhcpHost
12639 structural object class.
12641 <p
><strong
>Conclusion
</strong
></p
>
12643 <p
>The PowerDNS implementation seem to be very flexible when it come
12644 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
12645 come to the the LDAP structure, the
"strict
" mode is very flexible,
12646 allowing DNS objects to be stored anywhere under the base cn specified
12647 in the configuration.
</p
>
12649 <p
>The DHCP implementation on the other hand is very inflexible, both
12650 regarding which LDAP schemas to use and which LDAP structure to use.
12651 I guess one could implement ones own schema, as long as the
12652 objectclasses and attributes have the names used, but this do not
12653 really help when the DHCP subtree need to have a fairly fixed
12654 structure.
</p
>
12656 <p
>Based on the observed behaviour, I suspect a LDAP structure like
12657 this might work for Debian Edu:
</p
>
12659 <blockquote
><pre
>
12661 cn=machine-info (dhcpService) - dhcpServiceDN points here
12662 cn=dhcp (dhcpServer)
12663 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
12664 cn=
10.0.2.0 (dhcpSubnet)
12665 cn=group1 (dhcpGroup/dhcpOptions)
12666 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
12667 cn=
192.168.0.0 (dhcpSubnet)
12668 cn=group1 (dhcpGroup/dhcpOptions)
12669 ou=machines - PowerDNS base points here
12670 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
12671 </pre
></blockquote
>
12673 <P
>This is not tested yet. If the DHCP server require the dhcpHost
12674 entries to be in the dhcpGroup subtrees, the entries can be stored
12675 there instead of a common machines subtree, and the PowerDNS base
12676 would have to be moved one level up to the machine-info subtree.
</p
>
12678 <p
>The combined object under the machines subtree would look something
12679 like this:
</p
>
12681 <blockquote
><pre
>
12682 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
12685 objectClass: dhcpHost
12686 objectclass: domainrelatedobject
12687 objectclass: dnsDomainAux
12688 associateddomain: hostname.intern
12689 arecord:
10.11.12.13
12690 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
12691 dhcpStatements: fixed-address hostname.intern
12692 </pre
></blockquote
>
12694 </p
>One could even add the LTSP configuration associated with a given
12695 machine, as long as the required attributes are available in a
12696 auxiliary object class.
</p
>
12701 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
12702 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
12703 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
12704 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
12705 <description><p
>For a while now, I have wanted to find a way to change the DNS and
12706 DHCP services in Debian Edu to use the same LDAP objects for a given
12707 computer, to avoid the possibility of having a inconsistent state for
12708 a computer in LDAP (as in DHCP but no DNS entry or the other way
12709 around) and make it easier to add computers to LDAP.
</p
>
12711 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
12712 information finally found a solution that seem to work.
</p
>
12714 <p
>The old setup required three LDAP objects for a given computer.
12715 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
12716 we switch powerdns to use its strict LDAP method (ldap-method=strict
12717 in pdns-debian-edu.conf), the forward and reverse DNS entries are
12718 merged into one while making it impossible to transfer the reverse map
12719 to a slave DNS server.
</p
>
12721 <p
>If we also replace the object class used to get the DNS related
12722 attributes to one allowing these attributes to be combined with the
12723 dhcphost object class, we can merge the DNS and DHCP entries into one.
12724 I
've written such object class in the dnsdomainaux.schema file (need
12725 proper OIDs, but that is a minor issue), and tested the setup. It
12726 seem to work.
</p
>
12728 <p
>With this test setup in place, we can get away with one LDAP object
12729 for both DNS and DHCP, and even the LTSP configuration I suggested in
12730 an earlier email. The combined LDAP object will look something like
12733 <blockquote
><pre
>
12734 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12736 objectClass: dhcphost
12737 objectclass: domainrelatedobject
12738 objectclass: dnsdomainaux
12739 associateddomain: hostname.intern
12740 arecord:
10.11.12.13
12741 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
12742 dhcpstatements: fixed-address hostname
12744 </pre
></blockquote
>
12746 <p
>The DNS server uses the associateddomain and arecord entries, while
12747 the DHCP server uses the dhcphwaddress and dhcpstatements entries
12748 before asking DNS to resolve the fixed-adddress. LTSP will use
12749 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
12751 <p
>I am not yet sure if I can get the DHCP server to look for its
12752 dhcphost in a different location, to allow us to put the objects
12753 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
12754 that. If I can
't figure out a way to do that, we can still get rid of
12755 the hosts subtree and move all its content into the DHCP Config tree
12756 (which probably should be renamed to be more related to the new
12757 content. I suspect cn=dnsdhcp,ou=services or something like that
12758 might be a good place to put it.
</p
>
12760 <p
>If you want to help out with implementing this for Debian Edu,
12761 please contact us on debian-edu@lists.debian.org.
</p
>
12766 <title>Idea for storing LTSP configuration in LDAP
</title>
12767 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
12768 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
12769 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
12770 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
12771 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
12772 clients, and that this can be used to fetch configuration from LDAP if
12773 Debian Edu choose to store configuration there.
</p
>
12775 <p
>Armed with this information, I got inspired and wrote a test module
12776 to get configuration from LDAP. The idea is to look up the MAC
12777 address of the client in LDAP, and look for attributes on the form
12778 ltspconfigsetting=value, and use this to export SETTING=value to the
12779 LTSP clients.
</p
>
12781 <p
>The goal is to be able to store the LTSP configuration attributes
12782 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
12783 allowing us to store all information about a computer in one place.
</p
>
12785 <p
>This is a untested draft implementation, and I welcome feedback on
12786 this approach. A real LDAP schema for the ltspClientAux objectclass
12787 need to be written. Comments, suggestions, etc?
</p
>
12789 <blockquote
><pre
>
12790 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
12792 # Fetch LTSP client settings from LDAP based on MAC address
12794 # Uses ethernet address as stored in the dhcpHost objectclass using
12795 # the dhcpHWAddress attribute or ethernet address stored in the
12796 # ieee802Device objectclass with the macAddress attribute.
12798 # This module is written to be schema agnostic, and only depend on the
12799 # existence of attribute names.
12801 # The LTSP configuration variables are saved directly using a
12802 # ltspConfig prefix and uppercasing the rest of the attribute name.
12803 # To set the SERVER variable, set the ltspConfigServer attribute.
12805 # Some LDAP schema should be created with all the relevant
12806 # configuration settings. Something like this should work:
12808 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
12811 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
12813 LDAPSERVER=$(debian-edu-ldapserver)
12814 if [
"$LDAPSERVER
" ] ; then
12815 LDAPBASE=$(debian-edu-ldapserver -b)
12816 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
12817 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
12818 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
12819 grep
'^ltspConfig
' | while read attr value ; do
12820 # Remove prefix and convert to upper case
12821 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
12822 # bass value on to clients
12823 eval
"$attr=$value; export $attr
"
12827 </pre
></blockquote
>
12829 <p
>I
'm not sure this shell construction will work, because I suspect
12830 the while block might end up in a subshell causing the variables set
12831 there to not show up in ltsp-config, but if that is the case I am sure
12832 the code can be restructured to make sure the variables are passed on.
12833 I expect that can be solved with some testing. :)
</p
>
12835 <p
>If you want to help out with implementing this for Debian Edu,
12836 please contact us on debian-edu@lists.debian.org.
</p
>
12838 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
12839 configuration in LDAP that was created around year
2000 by
12840 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
12841 Xperience, Inc.,
2000</a
>. I found its
12842 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
12843 personal home page over at redhat.com.
</p
>
12848 <title>jXplorer, a very nice LDAP GUI
</title>
12849 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
12850 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
12851 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
12852 <description><p
>Since
12853 <a href=
"https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
12854 last post
</a
> about available LDAP tools in Debian, I was told about a
12855 LDAP GUI that is even better than luma. The java application
12856 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
12857 moving LDAP objects and subtrees using drag-and-drop, and can
12858 authenticate using Kerberos. I have only tested the Kerberos
12859 authentication, but do not have a LDAP setup allowing me to rewrite
12860 LDAP with my test user yet. It is
12861 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
12862 Debian
</a
> testing and unstable at the moment. The only problem I
12863 have with it is how it handle errors. If something go wrong, its
12864 non-intuitive behaviour require me to go through some query work list
12865 and remove the failing query. Nothing big, but very annoying.
</p
>
12870 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
12871 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
12872 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
12873 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
12874 <description><p
>Here is a short update on my
<a
12875 href=
"https://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
12876 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
12877 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
12878 not reporting the status for KDE, because the upgrade crashes when
12879 aptitude try because of missing conflicts
12880 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
12881 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
12883 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
12884 complete list of the installed packages. Based on this I see these
12885 differences when I did a test run today. As usual, I do not really
12886 know what the correct set of packages would be, but thought it best to
12887 publish the difference.
</p
>
12889 <p
>Installed using apt-get, missing with aptitude
</p
>
12891 <blockquote
><p
>
12892 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
12893 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
12894 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
12895 libgtksourceview-common libpt-
1.10.10-plugins-alsa
12896 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
12897 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
12898 python-
4suite-xml python-eggtrayicon python-gtkhtml2
12899 python-gtkmozembed svgalibg1 xserver-xephyr zip
12900 </p
></blockquote
>
12902 <p
>Installed using apt-get, removed with aptitude
</p
>
12904 <blockquote
><p
>
12905 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
12906 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
12907 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
12908 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
12909 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
12910 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
12911 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
12912 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
12913 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
12914 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
12915 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
12916 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
12917 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
12918 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
12919 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
12920 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
12921 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
12922 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
12923 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
12924 mysql-common swfdec-gnome totem-gstreamer wodim
12925 </p
></blockquote
>
12927 <p
>Installed using aptitude, missing with apt-get
</p
>
12929 <blockquote
><p
>
12930 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
12931 python-gnomekeyring python-wnck rhythmbox-plugins xorg
12932 xserver-xorg-input-all xserver-xorg-input-evdev
12933 xserver-xorg-input-kbd xserver-xorg-input-mouse
12934 xserver-xorg-input-synaptics xserver-xorg-video-all
12935 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
12936 xserver-xorg-video-chips xserver-xorg-video-cirrus
12937 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12938 xserver-xorg-video-glint xserver-xorg-video-i128
12939 xserver-xorg-video-i740 xserver-xorg-video-mach64
12940 xserver-xorg-video-mga xserver-xorg-video-neomagic
12941 xserver-xorg-video-nouveau xserver-xorg-video-nv
12942 xserver-xorg-video-r128 xserver-xorg-video-radeon
12943 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
12944 xserver-xorg-video-s3 xserver-xorg-video-s3virge
12945 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
12946 xserver-xorg-video-sis xserver-xorg-video-sisusb
12947 xserver-xorg-video-tdfx xserver-xorg-video-tga
12948 xserver-xorg-video-trident xserver-xorg-video-tseng
12949 xserver-xorg-video-vesa xserver-xorg-video-vmware
12950 xserver-xorg-video-voodoo
12951 </p
></blockquote
>
12953 <p
>Installed using aptitude, removed with apt-get
</p
>
12955 <blockquote
><p
>
12956 deskbar-applet xserver-xorg xserver-xorg-core
12957 xserver-xorg-input-wacom xserver-xorg-video-intel
12958 xserver-xorg-video-openchrome
12959 </p
></blockquote
>
12961 <p
>I was told on IRC that the xorg-xserver package was
12962 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
12963 in git
</a
> today to try to get apt-get to not remove xorg completely.
12964 No idea when it hits Squeeze, but when it does I hope it will reduce
12965 the difference somewhat.
12970 <title>LUMA, a very nice LDAP GUI
</title>
12971 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
12972 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
12973 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
12974 <description><p
>The last few days I have been looking into the status of the LDAP
12975 directory in Debian Edu, and in the process I started to miss a GUI
12976 tool to browse the LDAP tree. The only one I was able to find in
12977 Debian/Squeeze and Lenny is
12978 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
12979 be a great tool to get a overview of the current LDAP directory
12980 populated by default in Skolelinux. Thanks to it, I have been able to
12981 find empty and obsolete subtrees, misplaced objects and duplicate
12982 objects. It will be installed by default in Debian/Squeeze. If you
12983 are working with LDAP, give it a go. :)
</p
>
12985 <p
>I did notice one problem with it I have not had time to report to
12986 the BTS yet. There is no .desktop file in the package, so the tool do
12987 not show up in the Gnome and KDE menus, but only deep down in in the
12988 Debian submenu in KDE. I hope that can be fixed before Squeeze is
12989 released.
</p
>
12991 <p
>I have not yet been able to get it to modify the tree yet. I would
12992 like to move objects and remove subtrees directly in the GUI, but have
12993 not found a way to do that with LUMA yet. So in the mean time, I use
12994 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
12996 <p
>If you have tips on other GUI tools for LDAP that might be useful
12997 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
12999 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
13000 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
13001 useful GUI alternative. It seem like a good tool, but is unmaintained
13002 in Debian and got a RC bug keeping it out of Squeeze. Unless that
13003 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
13008 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
13009 <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>
13010 <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>
13011 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
13012 <description><p
>A while back, I
13013 <a href=
"https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
13014 about the fact
</a
> that it is not possible with the provided schemas
13015 for storing DNS and DHCP information in LDAP to combine the two sets
13016 of information into one LDAP object representing a computer.
</p
>
13018 <p
>In the mean time, I discovered that a simple fix would be to make
13019 the dhcpHost object class auxiliary, to allow it to be combined with
13020 the dNSDomain object class, and thus forming one object for one
13021 computer when storing both DHCP and DNS information in LDAP.
</p
>
13023 <p
>If I understand this correctly, it is not safe to do this change
13024 without also changing the assigned number for the object class, and I
13025 do not know enough about LDAP schema design to do that properly for
13026 Debian Edu.
</p
>
13028 <p
>Anyway, for future reference, this is how I believe we could change
13030 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
13031 schema
</a
> to solve at least part of the problem with the LDAP schemas
13032 available today from IETF.
</p
>
13035 --- dhcp.schema (revision
65192)
13036 +++ dhcp.schema (working copy)
13037 @@ -
376,
7 +
376,
7 @@
13038 objectclass (
2.16.840.1.113719.1.203.6.6
13039 NAME
'dhcpHost
'
13040 DESC
'This represents information about a particular client
'
13042 + SUP top AUXILIARY
13044 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
13045 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
13048 <p
>I very much welcome clues on how to do this properly for Debian
13049 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
13050 package, and should thus be free to rewrite it as we see fit.
</p
>
13052 <p
>If you want to help out with implementing this for Debian Edu,
13053 please contact us on debian-edu@lists.debian.org.
</p
>
13058 <title>Calling tasksel like the installer, while still getting useful output
</title>
13059 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
13060 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
13061 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
13062 <description><p
>A few times I have had the need to simulate the way tasksel
13063 installs packages during the normal debian-installer run. Until now,
13064 I have ended up letting tasksel do the work, with the annoying problem
13065 of not getting any feedback at all when something fails (like a
13066 conffile question from dpkg or a download that fails), using code like
13069 <blockquote
><pre
>
13070 export DEBIAN_FRONTEND=noninteractive
13071 tasksel --new-install
13072 </pre
></blockquote
>
13074 This would invoke tasksel, let its automatic task selection pick the
13075 tasks to install, and continue to install the requested tasks without
13076 any output what so ever.
13078 Recently I revisited this problem while working on the automatic
13079 package upgrade testing, because tasksel would some times hang without
13080 any useful feedback, and I want to see what is going on when it
13081 happen. Then it occured to me, I can parse the output from tasksel
13082 when asked to run in test mode, and use that aptitude command line
13083 printed by tasksel then to simulate the tasksel run. I ended up using
13086 <blockquote
><pre
>
13087 export DEBIAN_FRONTEND=noninteractive
13088 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
13090 </pre
></blockquote
>
13092 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
13093 --without-recommends -o APT::Install-Recommends=no -y install
13094 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
13095 ~pimportant
</tt
>", which will install the gnome desktop task, the
13096 laptop task and all packages with priority standard , required and
13097 important, just like tasksel would have done it during
13098 installation.
</p
>
13100 <p
>A better approach is probably to extend tasksel to be able to
13101 install packages without using debconf-apt-progress, for use cases
13102 like this.
</p
>
13107 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
13108 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
13109 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
13110 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
13111 <description><p
>My
13112 <a href=
"https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
13113 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
13114 finally made the upgrade logs available from
13115 <a href=
"https://people.skolelinux.org/pere/debian-upgrade-testing/
">https://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
13116 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
13117 apt and aptitude, and found their differences interesting. This time
13118 I will only focus on their removal plans.
</p
>
13120 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
13121 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
13122 surprising part is that it want to remove xorg and all
13123 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
13124 sure why. When asking aptitude to do the same, it want to remove
129
13125 packages, but most of them are library packages I suspect are no
13126 longer needed. Both of them want to remove bluetooth packages, which
13127 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
13129 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
13130 which seem like a bad idea and xorg the same way as with Gnome. Asking
13131 aptitude for the same, it wants to remove
192 packages, none which are
13132 too surprising.
</p
>
13134 <p
>I guess the removal of xorg during upgrades should be investigated
13135 and avoided, and perhaps others as well. Here are the complete list
13136 of planned removals. The complete logs is available from the URL
13137 above. Note if you want to repeat these tests, that the upgrade test
13138 for kde+apt-get hung in the tasksel setup because of dpkg asking
13139 conffile questions. No idea why. I worked around it by using
13140 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
13141 continue.
</p
>
13143 <p
><b
>apt-get gnome
72</b
>
13144 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
13145 gnome-desktop-environment gnome-network-admin gtkhtml3.14
13146 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
13147 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
13148 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
13149 serpentine swfdec-mozilla update-manager xorg xserver-xorg
13150 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
13151 xserver-xorg-input-kbd xserver-xorg-input-mouse
13152 xserver-xorg-input-synaptics xserver-xorg-input-wacom
13153 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
13154 xserver-xorg-video-ati xserver-xorg-video-chips
13155 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
13156 xserver-xorg-video-dummy xserver-xorg-video-fbdev
13157 xserver-xorg-video-glint xserver-xorg-video-i128
13158 xserver-xorg-video-i740 xserver-xorg-video-imstt
13159 xserver-xorg-video-intel xserver-xorg-video-mach64
13160 xserver-xorg-video-mga xserver-xorg-video-neomagic
13161 xserver-xorg-video-nsc xserver-xorg-video-nv
13162 xserver-xorg-video-openchrome xserver-xorg-video-r128
13163 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
13164 xserver-xorg-video-rendition xserver-xorg-video-s3
13165 xserver-xorg-video-s3virge xserver-xorg-video-savage
13166 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
13167 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
13168 xserver-xorg-video-tga xserver-xorg-video-trident
13169 xserver-xorg-video-tseng xserver-xorg-video-v4l
13170 xserver-xorg-video-vesa xserver-xorg-video-vga
13171 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
13172 xulrunner-
1.9-gnome-support
</p
>
13174 <p
><b
>aptitude gnome
129</b
>
13176 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
13177 djvulibre-desktop finger gnome-app-install gnome-mount
13178 gnome-network-admin gnome-spell gnome-vfs-obexftp
13179 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
13180 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
13181 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
13182 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
13183 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
13184 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
13185 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
13186 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
13187 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
13188 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
13189 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
13190 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
13191 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
13192 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
13193 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
13194 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
13195 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
13196 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
13197 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
13198 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
13199 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
13200 openoffice.org-writer2latex openssl-blacklist p7zip
13201 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
13202 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
13203 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
13204 swfdec-mozilla totem-gstreamer update-manager wodim
13205 xserver-xorg-video-cyrix xserver-xorg-video-imstt
13206 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
13209 <p
><b
>apt-get kde
82</b
>
13211 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
13212 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
13213 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
13214 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
13215 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
13216 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
13217 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
13218 xserver-xorg-input-kbd xserver-xorg-input-mouse
13219 xserver-xorg-input-synaptics xserver-xorg-input-wacom
13220 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
13221 xserver-xorg-video-ati xserver-xorg-video-chips
13222 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
13223 xserver-xorg-video-dummy xserver-xorg-video-fbdev
13224 xserver-xorg-video-glint xserver-xorg-video-i128
13225 xserver-xorg-video-i740 xserver-xorg-video-imstt
13226 xserver-xorg-video-intel xserver-xorg-video-mach64
13227 xserver-xorg-video-mga xserver-xorg-video-neomagic
13228 xserver-xorg-video-nsc xserver-xorg-video-nv
13229 xserver-xorg-video-openchrome xserver-xorg-video-r128
13230 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
13231 xserver-xorg-video-rendition xserver-xorg-video-s3
13232 xserver-xorg-video-s3virge xserver-xorg-video-savage
13233 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
13234 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
13235 xserver-xorg-video-tga xserver-xorg-video-trident
13236 xserver-xorg-video-tseng xserver-xorg-video-v4l
13237 xserver-xorg-video-vesa xserver-xorg-video-vga
13238 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
13240 <p
><b
>aptitude kde
192</b
>
13241 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
13242 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
13243 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
13244 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
13245 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
13246 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
13247 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
13248 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
13249 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
13250 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
13251 kghostview khelpcenter khexedit kiconedit kitchensync klatin
13252 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
13253 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
13254 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
13255 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
13256 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
13257 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
13258 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
13259 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
13260 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
13261 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
13262 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
13263 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
13264 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
13265 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
13266 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
13267 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
13268 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
13269 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
13270 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
13271 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
13272 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
13273 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
13274 texlive-common texlive-doc-base texlive-fonts-recommended
13275 xserver-xorg-video-cyrix xserver-xorg-video-imstt
13276 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
13277 xulrunner-
1.9</p
>
13283 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
13284 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
13285 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
13286 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
13287 <description><p
>The last few days I have done some upgrade testing in Debian, to
13288 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
13289 have been discovered and reported in the process
13290 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
13291 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
13292 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
13293 kdebase-workspace-data), and to get a more regular testing going on, I
13294 am working on a script to automate the test.
</p
>
13296 <p
>The idea is to create a Lenny chroot and use tasksel to install a
13297 Gnome or KDE desktop installation inside the chroot before upgrading
13298 it. To ensure no services are started in the chroot, a policy-rc.d
13299 script is inserted. To make sure tasksel believe it is to install a
13300 desktop on a laptop, the tasksel tests are replaced in the chroot
13301 (only acceptable because this is a throw-away chroot).
</p
>
13303 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
13304 currently always fail because udev refuses to upgrade with the kernel
13305 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
13306 is created. The bug report
13307 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
13308 this problem do not trigger in a chroot, but I touch the file anyway
13309 to make sure the upgrade go well. Testing on virtual and real
13310 hardware have failed me because of udev so far, and creating this file
13311 do the trick in such settings anyway. This is a
13312 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
13313 issue
</a
> and the current udev behaviour is intended by the udev
13314 maintainer because he lack the resources to rewrite udev to keep
13315 working with old kernels or something like that. I really wish the
13316 udev upstream would keep udev backwards compatible, to avoid such
13317 upgrade problem, but given that they fail to do so, I guess
13318 documenting the way out of this mess is the best option we got for
13319 Debian Squeeze.
</p
>
13321 <p
>Anyway, back to the task at hand, testing upgrades. This test
13322 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
13325 <blockquote
><pre
>
13329 if [
"$
1" ] ; then
13338 exec
&lt; /dev/null
13340 mirror=http://ftp.skolelinux.org/debian
13341 tmpdir=chroot-$from-upgrade-$to-$desktop
13343 debootstrap $from $tmpdir $mirror
13344 chroot $tmpdir aptitude update
13345 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
13349 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
13351 umount $tmpdir/proc
13353 mount -t proc proc $tmpdir/proc
13354 # Make sure proc is unmounted also on failure
13355 trap exit_cleanup EXIT INT
13357 chroot $tmpdir aptitude -y install debconf-utils
13359 # Make sure tasksel autoselection trigger. It need the test scripts
13360 # to return the correct answers.
13361 echo tasksel tasksel/desktop multiselect $desktop | \
13362 chroot $tmpdir debconf-set-selections
13364 # Include the desktop and laptop task
13365 for test in desktop laptop ; do
13366 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
13370 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
13373 DEBIAN_FRONTEND=noninteractive
13374 DEBIAN_PRIORITY=critical
13375 export DEBIAN_FRONTEND DEBIAN_PRIORITY
13376 chroot $tmpdir tasksel --new-install
13378 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
13379 chroot $tmpdir aptitude update
13380 touch $tmpdir/etc/udev/kernel-upgrade
13381 chroot $tmpdir aptitude -y dist-upgrade
13383 </pre
></blockquote
>
13385 <p
>I suspect it would be useful to test upgrades with both apt-get and
13386 with aptitude, but I have not had time to look at how they behave
13387 differently so far. I hope to get a cron job running to do the test
13388 regularly and post the result on the web. The Gnome upgrade currently
13389 work, while the KDE upgrade fail because of the bug in
13390 kdebase-workspace-data
</p
>
13392 <p
>I am not quite sure what kind of extract from the huge upgrade logs
13393 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
13394 post, so I will refrain from trying. I can report that for Gnome,
13395 aptitude report
760 packages upgraded,
448 newly installed,
129 to
13396 remove and
1 not upgraded and
1024MB need to be downloaded while for
13397 KDE the same numbers are
702 packages upgraded,
507 newly installed,
13398 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
13400 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
13401 is able to migrate to dependency based boot sequencing and parallel
13402 booting without a hitch. Was unsure if there were still bugs with
13403 packages failing to clean up their obsolete init.d script during
13404 upgrades, and no such problem seem to affect the Gnome desktop+laptop
13405 packages.
</p
>
13410 <title>Upstart or sysvinit - as init.d scripts see it
</title>
13411 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
13412 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
13413 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
13414 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
13415 scripts to migrate (some of) their operations to upstart job while
13416 keeping the init.d for hurd and kfreebsd. The packages with such
13417 needs will need a way to get their init.d scripts to behave
13418 differently when used with sysvinit and with upstart. Because of
13419 this, I had a look at the environment variables set when a init.d
13420 script is running under upstart, and when it is not.
</p
>
13422 <p
>With upstart, I notice these environment variables are set when a
13423 script is started from rcS.d/ (ignoring some irrelevant ones like
13424 COLUMNS):
</p
>
13426 <blockquote
><pre
>
13432 UPSTART_EVENTS=startup
13434 UPSTART_JOB=rc-sysinit
13435 </pre
></blockquote
>
13437 <p
>With sysvinit, these environment variables are set for the same
13440 <blockquote
><pre
>
13441 INIT_VERSION=sysvinit-
2.88
13446 </pre
></blockquote
>
13448 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
13449 sysvinit are not set by upstart. Not sure if it is intentional or not
13450 to not be compatible with sysvinit in this regard.
</p
>
13452 <p
>For scripts needing to behave differently when upstart is used,
13453 looking for the UPSTART_JOB environment variable seem to be a good
13459 <title>A manual for standards wars...
</title>
13460 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
13461 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
13462 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
13463 <description><p
>Via the
13464 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
13465 of Rob Weir
</a
> I came across the very interesting essay named
13466 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
13467 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
13468 following the standards wars of today.
</p
>
13473 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
13474 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
13475 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
13476 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
13477 <description><p
>When using sitesummary at a site to track machines, it is possible
13478 to get a list of the machine types in use thanks to the DMI
13479 information extracted from each machine. The script to do so is
13480 included in the sitesummary package, and here is example output from
13481 the Skolelinux build servers:
</p
>
13483 <blockquote
><pre
>
13484 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
13486 Dell Computer Corporation
1
13489 eserver xSeries
345 -[
8670M1X]-
1
13493 </pre
></blockquote
>
13495 <p
>The quality of the report depend on the quality of the DMI tables
13496 provided in each machine. Here there are Intel machines without model
13497 information listed with Intel as vendor and no model, and virtual Xen
13498 machines listed as [no-dmi-info]. One can add -l as a command line
13499 option to list the individual machines.
</p
>
13501 <p
>A larger list is
13502 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
13503 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
13504 provide the basic sitesummary report publicly. In their report there
13505 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
13506 their machines, and as sitesummary is available in both distributions,
13507 it is trivial to get all of them to report to the same central
13508 collector.
</p
>
13513 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
13514 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
13515 <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>
13516 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
13517 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
13518 start at boot when an NVidia video card is used is handled. The
13519 problem seem to be that the nvidia X.org driver uses a long time to
13520 initialize, and this duration is longer than kdm is configured to
13523 <p
>I came across two bugs related to this issue,
13524 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
13525 against initscripts and passed on to nvidia-glx when it became obvious
13526 that the nvidia drivers were involved, and
13527 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
13528 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
13530 <p
>To me, it seem that no-one is interested in actually solving the
13531 problem nvidia video card owners experience and make sure the Debian
13532 distribution work out of the box for these users. The nvidia driver
13533 maintainers expect kdm to be set up to wait longer, while kdm expect
13534 the nvidia driver maintainers to fix the driver to start faster, and
13535 while they wait for each other I guess the users end up switching to a
13536 distribution that work for them. I have no idea what the solution is,
13537 but I am pretty sure that waiting for each other is not it.
</p
>
13539 <p
>I wonder why we end up handling bugs this way.
</p
>
13544 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
13545 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
13546 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
13547 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
13548 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
13549 The feature seem to hold up pretty well, but three fairly serious
13550 issues are known and should be solved:
13552 <p
><ul
>
13554 <li
>The wicd package seen to
13555 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
13556 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
13557 parallel booting is enabled. No idea why, but the wicd maintainer
13558 seem to be on the case.
</li
>
13560 <li
>The nvidia X driver seem to
13561 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
13562 triggered more easily when parallel booting is in effect. The
13563 maintainer is on the case.
</li
>
13565 <li
>The sysv-rc package fail to properly enable dependency based boot
13566 sequencing (the shutdown is broken) when old file-rc users
13567 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
13568 sysv-rc. One way to solve it would be for file-rc to create
13569 /etc/init.d/.legacy-bootordering, and another is to try to make
13570 sysv-rc more robust. Will investigate some more and probably upload a
13571 workaround in sysv-rc to help those trying to move from file-rc to
13572 sysv-rc get a working shutdown.
</li
>
13574 </ul
></p
>
13576 <p
>All in all not many surprising issues, and all of them seem
13577 solvable before Squeeze is released. In addition to these there are
13578 some packages with bugs in their dependencies and run level settings,
13579 which I expect will be fixed in a reasonable time span.
</p
>
13581 <p
>If you report any problems with dependencies in init.d scripts to
13582 the BTS, please usertag the report to get it to show up at
13583 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13584 list of usertagged bugs related to this
</a
>.
</p
>
13586 <p
>Update: Correct bug number to file-rc issue.
</p
>
13591 <title>More flexible firmware handling in debian-installer
</title>
13592 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
13593 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
13594 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
13595 <description><p
>After a long break from debian-installer development, I finally
13596 found time today to return to the project. Having to spend less time
13597 working dependency based boot in debian, as it is almost complete now,
13598 definitely helped freeing some time.
</p
>
13600 <p
>A while back, I ran into a problem while working on Debian Edu. We
13601 include some firmware packages on the Debian Edu CDs, those needed to
13602 get disk and network controllers working. Without having these
13603 firmware packages available during installation, it is impossible to
13604 install Debian Edu on the given machine, and because our target group
13605 are non-technical people, asking them to provide firmware packages on
13606 an external medium is a support pain. Initially, I expected it to be
13607 enough to include the firmware packages on the CD to get
13608 debian-installer to find and use them. This proved to be wrong.
13609 Next, I hoped it was enough to symlink the relevant firmware packages
13610 to some useful location on the CD (tried /cdrom/ and
13611 /cdrom/firmware/). This also proved to not work, and at this point I
13612 found time to look at the debian-installer code to figure out what was
13613 going to work.
</p
>
13615 <p
>The firmware loading code is in the hw-detect package, and a closer
13616 look revealed that it would only look for firmware packages outside
13617 the installation media, so the CD was never checked for firmware
13618 packages. It would only check USB sticks, floppies and other
13619 "external
" media devices. Today I changed it to also look in the
13620 /cdrom/firmware/ directory on the mounted CD or DVD, which should
13621 solve the problem I ran into with Debian edu. I also changed it to
13622 look in /firmware/, to make sure the installer also find firmware
13623 provided in the initrd when booting the installer via PXE, to allow us
13624 to provide the same feature in the PXE setup included in Debian
13627 <p
>To make sure firmware deb packages with a license questions are not
13628 activated without asking if the license is accepted, I extended
13629 hw-detect to look for preinst scripts in the firmware packages, and
13630 run these before activating the firmware during installation. The
13631 license question is asked using debconf in the preinst, so this should
13632 solve the issue for the firmware packages I have looked at so far.
</p
>
13634 <p
>If you want to discuss the details of these features, please
13635 contact us on debian-boot@lists.debian.org.
</p
>
13640 <title>Parallellized boot is now the default in Debian/unstable
</title>
13641 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
13642 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
13643 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
13644 <description><p
>Since this evening, parallel booting is the default in
13645 Debian/unstable for machines using dependency based boot sequencing.
13646 Apparently the testing of concurrent booting has been wider than
13647 expected, if I am to believe the
13648 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
13649 on debian-devel@
</a
>, and I concluded a few days ago to move forward
13650 with the feature this weekend, to give us some time to detect any
13651 remaining problems before Squeeze is frozen. If serious problems are
13652 detected, it is simple to change the default back to sequential boot.
13653 The upload of the new sysvinit package also activate a new upstream
13656 More information about
13657 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13658 based boot sequencing
</a
> is available from the Debian wiki. It is
13659 currently possible to disable parallel booting when one run into
13660 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
13662 <blockquote
><pre
>
13664 </pre
></blockquote
>
13666 <p
>If you report any problems with dependencies in init.d scripts to
13667 the BTS, please usertag the report to get it to show up at
13668 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13669 list of usertagged bugs related to this
</a
>.
</p
>
13674 <title>Sitesummary tip: Listing MAC address of all clients
</title>
13675 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
13676 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
13677 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
13678 <description><p
>In the recent Debian Edu versions, the
13679 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
13680 system
</a
> is used to keep track of the machines in the school
13681 network. Each machine will automatically report its status to the
13682 central server after boot and once per night. The network setup is
13683 also reported, and using this information it is possible to get the
13684 MAC address of all network interfaces in the machines. This is useful
13685 to update the DHCP configuration.
</p
>
13687 <p
>To give some idea how to use sitesummary, here is a one-liner to
13688 ist all MAC addresses of all machines reporting to sitesummary. Run
13689 this on the collector host:
</p
>
13691 <blockquote
><pre
>
13692 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
13693 </pre
></blockquote
>
13695 <p
>This will list all MAC addresses assosiated with all machine, one
13696 line per machine and with space between the MAC addresses.
</p
>
13698 <p
>To allow system administrators easier job at adding static DHCP
13699 addresses for hosts, it would be possible to extend this to fetch
13700 machine information from sitesummary and update the DHCP and DNS
13701 tables in LDAP using this information. Such tool is unfortunately not
13702 written yet.
</p
>
13707 <title>systemd, an interesting alternative to upstart
</title>
13708 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
13709 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
13710 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
13711 <description><p
>The last few days a new boot system called
13712 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
13714 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
13716 to the free software world. I have not yet had time to play around
13717 with it, but it seem to be a very interesting alternative to
13718 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
13719 a good alternative for Debian when we are able to switch to an event
13720 based boot system. Tollef is
13721 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
13722 systemd into Debian, and I look forward to seeing how well it work. I
13723 like the fact that systemd handles init.d scripts with dependency
13724 information natively, allowing them to run in parallel where upstart
13725 at the moment do not.
</p
>
13727 <p
>Unfortunately do systemd have the same problem as upstart regarding
13728 platform support. It only work on recent Linux kernels, and also need
13729 some new kernel features enabled to function properly. This means
13730 kFreeBSD and Hurd ports of Debian will need a port or a different boot
13731 system. Not sure how that will be handled if systemd proves to be the
13732 way forward.
</p
>
13734 <p
>In the mean time, based on the
13735 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
13736 on debian-devel@
</a
> regarding parallel booting in Debian, I have
13737 decided to enable full parallel booting as the default in Debian as
13738 soon as possible (probably this weekend or early next week), to see if
13739 there are any remaining serious bugs in the init.d dependencies. A
13740 new version of the sysvinit package implementing this change is
13741 already in experimental. If all go well, Squeeze will be released
13742 with parallel booting enabled by default.
</p
>
13747 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
13748 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
13749 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
13750 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
13751 <description><p
>These days, the init.d script dependencies in Squeeze are quite
13752 complete, so complete that it is actually possible to run all the
13753 init.d scripts in parallell based on these dependencies. If you want
13754 to test your Squeeze system, make sure
13755 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13756 based boot sequencing
</a
> is enabled, and add this line to
13757 /etc/default/rcS:
</p
>
13759 <blockquote
><pre
>
13760 CONCURRENCY=makefile
13761 </pre
></blockquote
>
13763 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
13764 scripts in parallel using the dependency information stored in
13765 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
13766 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
13767 to try to start the kdm and gdm scripts as early as possible, and will
13768 start the facilities required by kdm or gdm as early as possible to
13769 make this happen.
</p
>
13771 <p
>Give it a try, and see if you like the result. If some services
13772 fail to start properly, it is most likely because they have incomplete
13773 init.d script dependencies in their startup script (or some of their
13774 dependent scripts have incomplete dependencies). Report bugs and get
13775 the package maintainers to fix it. :)
</p
>
13777 <p
>Running scripts in parallel could be the default in Debian when we
13778 manage to get the init.d script dependencies complete and correct. I
13779 expect we will get there in Squeeze+
1, if we get manage to test and
13780 fix the remaining issues.
</p
>
13782 <p
>If you report any problems with dependencies in init.d scripts to
13783 the BTS, please usertag the report to get it to show up at
13784 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13785 list of usertagged bugs related to this
</a
>.
</p
>
13790 <title>Debian has switched to dependency based boot sequencing
</title>
13791 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
13792 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
13793 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
13794 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
13795 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
13796 have been migrated to using dependency based boot sequencing. This
13797 conclude work me and others have been doing for the last three days.
13798 It feels great to see this finally part of the default Debian
13799 installation. Now we just need to weed out the last few problems that
13800 are bound to show up, to get everything ready for Squeeze.
</p
>
13802 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
13803 fixing the more fundamental problem of handing the event based
13804 non-predictable kernel in the early boot.
</p
>
13809 <title>Taking over sysvinit development
</title>
13810 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
13811 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
13812 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
13813 <description><p
>After several years of frustration with the lack of activity from
13814 the existing sysvinit upstream developer, I decided a few weeks ago to
13815 take over the package and become the new upstream. The number of
13816 patches to track for the Debian package was becoming a burden, and the
13817 lack of synchronization between the distribution made it hard to keep
13818 the package up to date.
</p
>
13820 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
13821 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
13822 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
13823 and Fedora), based on the patches currently in use in these
13824 distributions. We Debian maintainers plan to move to this tarball as
13825 the new upstream as soon as we find time to do the merge. Since the
13826 new tarball was created, we agreed with Werner at SuSe to make a new
13827 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
13828 development there. The project is registered and currently waiting
13829 for approval by the Savannah administrators, and as soon as it is
13830 approved, we will import the old versions from svn and continue
13831 working on the future release.
</p
>
13833 <p
>It is a bit ironic that this is done now, when some of the involved
13834 distributions are moving to upstart as a syvinit replacement.
</p
>
13839 <title>Debian boots quicker and quicker
</title>
13840 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
13841 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
13842 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
13843 <description><p
>I spent Monday and tuesday this week in London with a lot of the
13844 people involved in the boot system on Debian and Ubuntu, to see if we
13845 could find more ways to speed up the boot system. This was an Ubuntu
13847 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
13848 gathering
</a
>. It was quite productive. We also discussed the future
13849 of boot systems, and ways to handle the increasing number of boot
13850 issues introduced by the Linux kernel becoming more and more
13851 asynchronous and event base. The Ubuntu approach using udev and
13852 upstart might be a good way forward. Time will show.
</p
>
13854 <p
>Anyway, there are a few ways at the moment to speed up the boot
13855 process in Debian. All of these should be applied to get a quick
13860 <li
>Use dash as /bin/sh.
</li
>
13862 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
13863 clock is in UTC.
</li
>
13865 <li
>Install and activate the insserv package to enable
13866 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13867 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
13871 These points are based on the Google summer of code work done by
13872 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
13873 Villegas
</a
>.
13875 <p
>Support for makefile-style concurrency during boot was uploaded to
13876 unstable yesterday. When we tested it, we were able to cut
6 seconds
13877 from the boot sequence. It depend on very correct dependency
13878 declaration in all init.d scripts, so I expect us to find edge cases
13879 where the dependences in some scripts are slightly wrong when we start
13880 using this.
</p
>
13882 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
13883 introduced by Raphael Geissert today, one that could affect the
13884 startup speed as well. Instead of starting some scripts concurrently
13885 from rcS.d/ and another set of scripts from rc2.d/, it would be
13886 possible to run a of them in the same process. A quick way to test
13887 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
13888 insserv
'. Will need to test if that work. :)
</p
>
13893 <title>BSAs påstander om piratkopiering møter motstand
</title>
13894 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
13895 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
13896 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
13897 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
13898 programvareselskapene som Microsoft og Apple, publisert en rapport der
13899 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
13900 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
13902 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
13903 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
13904 dagene. Et spesielt interessant kommentar fra Sverige,
13905 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
13906 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
13909 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
13910 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
13911 företag.
"Man bör nog kanske inte se de här siffrorna som helt
13912 exakta
", säger BSAs Sverigechef John Hugosson.
13913 </blockquote
>
13915 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
13916 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
13917 piracy figures need a shot of reality
</a
> og
<a
13918 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
13919 Copyright Treaty Work?
</a
></p
>
13921 <p
>Fant lenkene via
<a
13922 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
13923 på Slashdot
</a
>.
</p
>
13928 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
13929 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
13930 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
13931 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
13932 <description><p
>Kom over
13933 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
13934 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
13935 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
13936 jobber til daglig. En rask opptelling forteller meg at vi har
490
13937 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
13938 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
13939 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
13944 <title>Kryptert harddisk - naturligvis
</title>
13945 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
13946 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
13947 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
13948 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
13949 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
13950 når en tar tap av arbeidstid, fortrolige dokumenter,
13951 personopplysninger og alt annet det innebærer. Det er ingen tvil om
13952 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
13953 til at jeg har kryptert harddisken på både kontormaskinen og min
13954 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13955 komme på avveie, den første informasjon relatert til jobben min ved
13956 Universitetet i Oslo, og den andre relatert til blant annet
13957 foreningsarbeide. Kryptering av diskene gjør at det er lite
13958 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13959 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13960 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13961 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13962 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13963 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13964 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
13965 det er gjort slik jeg gjør det er minimale, og gevinstene er
13966 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
13967 maskinen reinstalleres og alt er tapt.
</p
>
13969 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
13970 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
13971 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
13972 er for min del høyere enn gevinsten. Jeg tror oddsene for at
13973 f.eks. etteretningsorganisasjoner har glede av å titte på mine
13974 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
13975 gjøre det vanskeligere for angripere med kompetanse og ressurser er
13976 betydelige.
</p
>
13981 <title>Two projects that have improved the quality of free software a lot
</title>
13982 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
13983 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
13984 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
13985 <description><p
>There are two software projects that have had huge influence on the
13986 quality of free software, and I wanted to mention both in case someone
13987 do not yet know them.
</p
>
13989 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
13990 tool to detect and expose errors in the memory handling of programs.
13991 It is easy to use, all one need to do is to run
'valgrind program
',
13992 and it will report any problems on stdout. It is even better if the
13993 program include debug information. With debug information, it is able
13994 to report the source file name and line number where the problem
13995 occurs. It can report things like
'reading past memory block in file
13996 X line N, the memory block was allocated in file Y, line M
', and
13997 'using uninitialised value in control logic
'. This tool has made it
13998 trivial to investigate reproducible crash bugs in programs, and have
13999 reduced the number of this kind of bugs in free software a lot.
14001 <p
>The second one is
14002 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
14003 a source code checker. It is able to process the source of a program
14004 and find problems in the logic without running the program. It
14005 started out as the Stanford Checker and became well known when it was
14006 used to find bugs in the Linux kernel. It is now a commercial tool
14007 and the company behind it is running
14008 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
14009 free software community, where a lot of free software projects get
14010 their source checked for free. Several thousand defects have been
14011 found and fixed so far. It can find errors like
'lock L taken in file
14012 X line N is never released if exiting in line M
', or
'the code in file
14013 Y lines O to P can never be executed
'. The projects included in the
14014 community service project have managed to get rid of a lot of
14015 reliability problems thanks to Coverity.
</p
>
14017 <p
>I believe tools like this, that are able to automatically find
14018 errors in the source, are vital to improve the quality of software and
14019 make sure we can get rid of the crashing and failing software we are
14020 surrounded by today.
</p
>
14025 <title>No patch is not better than a useless patch
</title>
14026 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
14027 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
14028 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
14029 <description><p
>Julien Blache
14030 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
14031 patch is better than a useless patch
</a
>. I completely disagree, as a
14032 patch allow one to discuss a concrete and proposed solution, and also
14033 prove that the issue at hand is important enough for someone to spent
14034 time on fixing it. No patch do not provide any of these positive
14035 properties.
</p
>
14040 <title>Standardize on protocols and formats, not vendors and applications
</title>
14041 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
14042 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
14043 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
14044 <description><p
>Where I work at the University of Oslo, one decision stand out as a
14045 very good one to form a long lived computer infrastructure. It is the
14046 simple one, lost by many in todays computer industry: Standardize on
14047 open network protocols and open exchange/storage formats, not applications.
14048 Applications come and go, while protocols and files tend to stay, and
14049 thus one want to make it easy to change application and vendor, while
14050 avoiding conversion costs and locking users to a specific platform or
14051 application.
</p
>
14053 <p
>This approach make it possible to replace the client applications
14054 independently of the server applications. One can even allow users to
14055 use several different applications as long as they handle the selected
14056 protocol and format. In the normal case, only one client application
14057 is recommended and users only get help if they choose to use this
14058 application, but those that want to deviate from the easy path are not
14059 blocked from doing so.
</p
>
14061 <p
>It also allow us to replace the server side without forcing the
14062 users to replace their applications, and thus allow us to select the
14063 best server implementation at any moment, when scale and resouce
14064 requirements change.
</p
>
14066 <p
>I strongly recommend standardizing - on open network protocols and
14067 open formats, but I would never recommend standardizing on a single
14068 application that do not use open network protocol or open formats.
</p
>
14073 <title>Returning from Skolelinux developer gathering
</title>
14074 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
14075 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
14076 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
14077 <description><p
>I
'm sitting on the train going home from this weekends Debian
14078 Edu/Skolelinux development gathering. I got a bit done tuning the
14079 desktop, and looked into the dynamic service location protocol
14080 implementation avahi. It look like it could be useful for us. Almost
14081 30 people participated, and I believe it was a great environment to
14082 get to know the Skolelinux system. Walter Bender, involved in the
14083 development of the Sugar educational platform, presented his stuff and
14084 also helped me improve my OLPC installation. He also showed me that
14085 his Turtle Art application can be used in standalone mode, and we
14086 agreed that I would help getting it packaged for Debian. As a
14087 standalone application it would be great for Debian Edu. We also
14088 tried to get the video conferencing working with two OLPCs, but that
14089 proved to be too hard for us. The application seem to need more work
14090 before it is ready for me. I look forward to getting home and relax
14096 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
14097 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
14098 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
14099 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
14100 <description><p
>The state of standardized LDAP schemas on Linux is far from
14101 optimal. There is RFC
2307 documenting one way to store NIS maps in
14102 LDAP, and a modified version of this normally called RFC
2307bis, with
14103 some modifications to be compatible with Active Directory. The RFC
14104 specification handle the content of a lot of system databases, but do
14105 not handle DNS zones and DHCP configuration.
</p
>
14107 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
14108 we would like to store information about users, SMB clients/hosts,
14109 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
14110 and LTSP configuration in LDAP. These objects have a lot in common,
14111 but with the current LDAP schemas it is not possible to have one
14112 object per entity. For example, one need to have at least three LDAP
14113 objects for a given computer, one with the SMB related stuff, one with
14114 DNS information and another with DHCP information. The schemas
14115 provided for DNS and DHCP are impossible to combine into one LDAP
14116 object. In addition, it is impossible to implement quick queries for
14117 netgroup membership, because of the way NIS triples are implemented.
14118 It just do not scale. I believe it is time for a few RFC
14119 specifications to cleam up this mess.
</p
>
14121 <p
>I would like to have one LDAP object representing each computer in
14122 the network, and this object can then keep the SMB (ie host key), DHCP
14123 (mac address/name) and DNS (name/IP address) settings in one place.
14124 It need to be efficently stored to make sure it scale well.
</p
>
14126 <p
>I would also like to have a quick way to map from a user or
14127 computer and to the net group this user or computer is a member.
</p
>
14129 <p
>Active Directory have done a better job than unix heads like myself
14130 in this regard, and the unix side need to catch up. Time to start a
14131 new IETF work group?
</p
>
14136 <title>Endelig er Debian Lenny gitt ut
</title>
14137 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
14138 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
14139 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
14140 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
14141 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
14142 Et langt steg videre for Debian-prosjektet, og en rekke nye
14143 programpakker blir nå tilgjengelig for de av oss som bruker den
14144 stabile utgaven av Debian. Neste steg er nå å få
14145 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
14146 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
14147 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
14148 slippes løs på skolene. Takk til alle debian-utviklerne som har
14149 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
14150 bootsekvens tilgjengelig i stabil utgave, vha pakken
14151 <tt
>insserv
</tt
>.
</p
>
14156 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
14157 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
14158 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
14159 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
14160 <description><p
>This weekend we had a small developer gathering for Debian Edu in
14161 Oslo. Most of Saturday was used for the general assemly for the
14162 member organization, but the rest of the weekend I used to tune the
14163 LTSP installation. LTSP now work out of the box on the
10-network.
14164 Acer Aspire One proved to be a very nice thin client, with both
14165 screen, mouse and keybard in a small box. Was working on getting the
14166 diskless workstation setup configured out of the box, but did not
14167 finish it before the weekend was up.
</p
>
14169 <p
>Did not find time to look at the
4 VGA cards in one box we got from
14170 the Brazilian group, so that will have to wait for the next
14171 development gathering. Would love to have the Debian Edu installer
14172 automatically detect and configure a multiseat setup when it find one
14173 of these cards.
</p
>
14178 <title>The sorry state of multimedia browser plugins in Debian
</title>
14179 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
14180 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
14181 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
14182 <description><p
>Recently I have spent some time evaluating the multimedia browser
14183 plugins available in Debian Lenny, to see which one we should use by
14184 default in Debian Edu. We need an embedded video playing plugin with
14185 control buttons to pause or stop the video, and capable of streaming
14186 all the multimedia content available on the web. The test results and
14187 notes are available on
14188 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
14189 Debian wiki
</a
>. I was surprised how few of the plugins are able to
14190 fill this need. My personal video player favorite, VLC, has a really
14191 bad plugin which fail on a lot of the test pages. A lot of the MIME
14192 types I would expect to work with any free software player (like
14193 video/ogg), just do not work. And simple formats like the
14194 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
14195 totem and vlc plugins. I hope the situation will improve soon. No
14196 wonder sites use the proprietary Adobe flash to play video.
</p
>
14198 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
14199 be the only one fitting our needs. :/
</p
>