blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="https://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="https://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="https://people.skolelinux.org/pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html">The 2024 LinuxCNC Norwegian developer gathering</a></div>
  24       <div class="date">31st May 2024</div>
  25       <div class="body"><p><a href="https://linuxcnc.org/">The LinuxCNC project</a> is still
  26 going strong.  And I believe this great software system for numerical control of
  27 machines such as milling machines, lathes, plasma cutters, routers,
  28 cutting machines, robots and hexapods, would do even better with more
  29 in-person developer gatherings, so we plan to organise such gathering
  30 this summer too.</p>
  31
  32 <p>The Norwegian LinuxCNC developer gathering take place the weekend
  33 Friday July 5th to 7th this year, and is open for everyone interested
  34 in contributing to LinuxCNC and free software manufacturing.  Up to
  35 date information about the gathering can be found in
  36 <a href="https://sourceforge.net/p/emc/mailman/emc-developers/thread/123eaae0-f3b9-4170-a251-b7d608f1e974%40bofh.no/">the
  37 developer mailing list thread</a> where the gathering was announced.
  38 Thanks to the good people at
  39
  40 <a href="https://www.debian.org/">Debian</a> as well as leftover money
  41 from last years gathering from
  42 <a href="https://www.redpill-linpro.com/">Redpill-Linpro</a> and
  43 <a href="https://www.nuugfoundation.no/no/">NUUG Foundation</a>, we
  44 have enough sponsor funds to pay for food, and probably also shelter
  45 for the people traveling from afar to join us.  If you would like to
  46 join the gathering, get in touch and add your details on
  47 <a href="https://pad.efn.no/p/linuxcnc-2024-norway">the pad</a>.</p>
  48
  49 <p>As usual, if you use Bitcoin and want to show your support of my
  50 activities, please send Bitcoin donations to my address
  51 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  52 </div>
  53       <div class="tags">
  54
  55
  56         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc</a>.
  57
  58
  59       </div>
  60     </div>
  61     <div class="padding"></div>
  62
  63     <div class="entry">
  64       <div class="title"><a href="https://people.skolelinux.org/pere/blog/45_orphaned_Debian_packages_moved_to_git__391_to_go.html">45 orphaned Debian packages moved to git, 391 to go</a></div>
  65       <div class="date">25th April 2024</div>
  66       <div class="body"><p>Nine days ago, I started migrating orphaned Debian packages with no
  67 version control system listed in debian/control of the source to git.
  68 At the time there were 438 such packages.  Now there are 391,
  69 according to the UDD.  In reality it is slightly less, as there is a
  70 delay between uploads and UDD updates.  In the nine days since, I have
  71 thus been able to work my way through ten percent of the packages.  I
  72 am starting to run out of steam, and hope someone else will also help
  73 brushing some dust of these packages.  Here is a recipe how to do it.
  74
  75 I start by picking a random package by querying the UDD for a list of
  76 10 random packages from the set of remaining packages:
  77
  78 <blockquote><pre>
  79 PGPASSWORD="udd-mirror" psql --port=5432 --host=udd-mirror.debian.net \
  80   --username=udd-mirror udd -c "select source from sources \
  81    where release = 'sid' and (vcs_url ilike '%anonscm.debian.org%' \
  82    OR vcs_browser ilike '%anonscm.debian.org%' or vcs_url IS NULL \
  83    OR vcs_browser IS NULL) AND maintainer ilike '%packages@qa.debian.org%' \
  84    order by random() limit 10;"
  85 </pre></blockquote>
  86
  87 <p>Next, I visit http://salsa.debian.org/debian and search for the
  88 package name, to ensure no git repository already exist.  If it does,
  89 I clone it and try to get it to an uploadable state, and add the Vcs-*
  90 entries in d/control to make the repository more widely known.  These
  91 packages are a minority, so I will not cover that use case here.</p>
  92
  93 <p>For packages without an existing git repository, I run the
  94 following script <tt>debian-snap-to-salsa</tt> to prepare a git
  95 repository with the existing packaging.</p>
  96
  97 <blockquote><pre>
  98 #!/bin/sh
  99 #
 100 # See also https://bugs.debian.org/804722#31
 101
 102 set -e
 103
 104 # Move to this Standards-Version.
 105 SV_LATEST=4.7.0
 106
 107 PKG="$1"
 108
 109 if [ -z "$PKG" ]; then
 110     echo "usage: $0 <pkgname>"
 111     exit 1
 112 fi
 113
 114 if [ -e "${PKG}-salsa" ]; then
 115     echo "error: ${PKG}-salsa already exist, aborting."
 116     exit 1
 117 fi
 118
 119 if [ -z "ALLOWFAILURE" ] ; then
 120     ALLOWFAILURE=false
 121 fi
 122
 123 # Fetch every snapshotted source package.  Manually loop until all
 124 # transfers succeed, as 'gbp import-dscs --debsnap' do not fail on
 125 # download failures.
 126 until debsnap --force -v $PKG || $ALLOWFAILURE ; do sleep 1; done
 127 mkdir ${PKG}-salsa; cd ${PKG}-salsa
 128 git init
 129
 130 # Specify branches to override any debian/gbp.conf file present in the
 131 # source package.
 132 gbp import-dscs  --debian-branch=master --upstream-branch=upstream \
 133     --pristine-tar ../source-$PKG/*.dsc
 134
 135 # Add Vcs pointing to Salsa Debian project (must be manually created
 136 # and pushed to).
 137 if ! grep -q ^Vcs- debian/control ; then
 138     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
 139     git commit -m "Updated vcs in d/control to Salsa." debian/control
 140 fi
 141
 142 # Tell gbp to enforce the use of pristine-tar.
 143 inifile +inifile debian/gbp.conf +create +section DEFAULT +key pristine-tar +value True
 144 git add debian/gbp.conf
 145 git commit -m "Added d/gbp.conf to enforce the use of pristine-tar." debian/gbp.conf
 146
 147 # Update to latest Standards-Version.
 148 SV="$(grep ^Standards-Version: debian/control|awk '{print $2}')"
 149 if [ $SV_LATEST != $SV ]; then
 150     sed -i "s/\(Standards-Version: \)\(.*\)/\1$SV_LATEST/" debian/control
 151     git commit -m "Updated Standards-Version from $SV to $SV_LATEST." debian/control
 152 fi
 153
 154 if grep -q pkg-config debian/control; then
 155     sed -i s/pkg-config/pkgconf/ debian/control
 156     git commit -m "Replaced obsolete pkg-config build dependency with pkgconf." debian/control
 157 fi
 158
 159 if grep -q libncurses5-dev debian/control; then
 160     sed -i s/libncurses5-dev/libncurses-dev/ debian/control
 161     git commit -m "Replaced obsolete libncurses5-dev build dependency with libncurses-dev." debian/control
 162 fi
 163 </pre></blockquote>
 164
 165 Some times the debsnap script fail to download some of the versions.
 166 In those cases I investigate, and if I decide the failing versions
 167 will not be missed, I call it using ALLOWFAILURE=true to ignore the
 168 problem and create the git repository anyway.</p>
 169
 170 <p>With the git repository in place, I do a test build (gbp
 171 buildpackage) to ensure the build is actually working.  If it does not
 172 I pick a different package, or if the build failure is trivial to fix,
 173 I fix it before continuing.  At this stage I revisit
 174 http://salsa.debian.org/debian and create the project under this group
 175 for the package.  I then follow the instructions to publish the local
 176 git repository.  Here is from a recent example:</p>
 177
 178 <blockquote><pre>
 179 git remote add origin git@salsa.debian.org:debian/perl-byacc.git
 180 git push --set-upstream origin master upstream pristine-tar
 181 git push --tags
 182 </pre></blockquote>
 183
 184 <p>With a working build, I have a look at the build rules if I want to
 185 remove some more dust.  I normally try to move to debhelper compat
 186 level 13, which involves removing debian/compat and modifying
 187 debian/control to build depend on debhelper-compat (=13).  I also test
 188 with 'Rules-Requires-Root: no' in debian/control and verify in
 189 debian/rules that hardening is enabled, and include all of these if
 190 the package still build.  If it fail to build with level 13, I try
 191 with 12, 11, 10 and so on until I find a level where it build, as I do
 192 not want to spend a lot of time fixing build issues.</p>
 193
 194 <p>Some times, when I feel inspired, I make sure debian/copyright is
 195 converted to the machine readable format, often by starting with
 196 'debhelper -cc' and then cleaning up the autogenerated content until
 197 it matches realities.  If I feel like it, I might also clean up
 198 non-dh-based debian/rules files to use the short style dh build
 199 rules.</p>
 200
 201 <p>Once I have removed all the dust I care to process for the package,
 202 I run 'gbp dch' to generate a debian/changelog entry based on the
 203 commits done so far, run 'dch -r' to switch from 'UNRELEASED' to
 204 'unstable' and get an editor to make sure the 'QA upload' marker is in
 205 place and that all long commit descriptions are wrapped into sensible
 206 lengths, run 'debcommit --release -a' to commit and tag the new
 207 debian/changelog entry, run 'debuild -S' to build a source only
 208 package, and 'dput ../perl-byacc_2.0-10_source.changes' to do the
 209 upload.  During the entire process, and many times per step, I run
 210 'debuild' to verify the changes done still work.  I also some times
 211 verify the set of built files using 'find debian' to see if I can spot
 212 any problems (like no file in usr/bin any more or empty package).  I
 213 also try to fix all lintian issues reported at the end of each
 214 'debuild' run.</p>
 215
 216 <p>If I find Debian specific patches, I try to ensure their metadata
 217 is fairly up to date and some times I even try to reach out to
 218 upstream, to make the upstream project aware of the patches.  Most of
 219 my emails bounce, so the success rate is low.  For projects with no
 220 Homepage entry in debian/control I try to track down one, and for
 221 packages with no debian/watch file I try to create one.  But at least
 222 for some of the packages I have been unable to find a functioning
 223 upstream, and must skip both of these.</p>
 224
 225 <p>If I could handle ten percent in nine days, twenty people could
 226 complete the rest in less then five days.  I use approximately twenty
 227 minutes per package, when I have twenty minutes spare time to spend.
 228 Perhaps you got twenty minutes to spare too?</p>
 229
 230 <p>As usual, if you use Bitcoin and want to show your support of my
 231 activities, please send Bitcoin donations to my address
 232 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 233
 234 <p><strong>Update 2024-05-04:</strong> There is
 235 <a href="https://people.skolelinux.org/pere/blog/images/2024-05-04-debian-snap-to-salsa.sh">an
 236 updated edition of my migration script</a>, last updated
 237 2024-05-04.</p>
 238 </div>
 239       <div class="tags">
 240
 241
 242         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 243
 244
 245       </div>
 246     </div>
 247     <div class="padding"></div>
 248
 249     <div class="entry">
 250       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html">RAID status from LSI Megaraid controllers in Debian</a></div>
 251       <div class="date">17th April 2024</div>
 252       <div class="body"><p>I am happy to report that
 253 <a href="https://github.com/namiltd/megactl">the megactl package</a>,
 254 useful to fetch RAID status when using the LSI Megaraid controller,
 255 now is available in Debian.  It passed NEW a few days ago, and is now
 256 <a href="https://tracker.debian.org/pkg/megactl">available in
 257 unstable</a>, and probably showing up in testing in a weeks time.  The
 258 new version should provide Appstream hardware mapping and should
 259 integrate nicely with isenkram.</p>
 260
 261 <p>As usual, if you use Bitcoin and want to show your support of my
 262 activities, please send Bitcoin donations to my address
 263 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 264
 265 </div>
 266       <div class="tags">
 267
 268
 269         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
 270
 271
 272       </div>
 273     </div>
 274     <div class="padding"></div>
 275
 276     <div class="entry">
 277       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html">Time to move orphaned Debian packages to git</a></div>
 278       <div class="date">14th April 2024</div>
 279       <div class="body"><p>There are several packages in Debian without a associated git
 280 repository with the packaging history.  This is unfortunate and it
 281 would be nice if more of these would do so.  Quote a lot of these are
 282 without a maintainer, ie listed as maintained by the
 283 '<a href="https://qa.debian.org/developer.php?email=packages%40qa.debian.org">Debian
 284 QA Group</a>' place holder.  In fact, 438 packages have this property
 285 according to UDD (<tt>SELECT source FROM sources WHERE release = 'sid'
 286 AND (vcs_url ilike '%anonscm.debian.org%' OR vcs_browser ilike
 287 '%anonscm.debian.org%' or vcs_url IS NULL OR vcs_browser IS NULL) AND
 288 maintainer ilike '%packages@qa.debian.org%';</tt>).  Such packages can
 289 be updated without much coordination by any Debian developer, as they
 290 are considered orphaned.</p>
 291
 292 <p>To try to improve the situation and reduce the number of packages
 293 without associated git repository, I started a few days ago to search
 294 out candiates and provide them with a git repository under the
 295 'debian' collaborative Salsa project.  I started with the packages
 296 pointing to obsolete Alioth git repositories, and am now working my
 297 way across the ones completely without git references.  In addition to
 298 updating the Vcs-* debian/control fields, I try to update
 299 Standards-Version, debhelper compat level, simplify d/rules, switch to
 300 Rules-Requires-Root: no and fix lintian issues reported.  I only
 301 implement those that are trivial to fix, to avoid spending too much
 302 time on each orphaned package.  So far my experience is that it take
 303 aproximately 20 minutes to convert a package without any git
 304 references, and a lot more for packages with existing git repositories
 305 incompatible with git-buildpackages.</p>
 306
 307 <p>So far I have converted 10 packages, and I will keep going until I
 308 run out of steam.  As should be clear from the numbers, there is
 309 enough packages remaining for more people to do the same without
 310 stepping on each others toes.  I find it useful to start by searching
 311 for a git repo already on salsa, as I find that some times a git repo
 312 has already been created, but no new version is uploaded to Debian
 313 yet.  In those cases I start with the existing git repository.  I
 314 convert to the git-buildpackage+pristine-tar workflow, and ensure a
 315 debian/gbp.conf file with "pristine-tar=True" is added early, to avoid
 316 uploading a orig.tar.gz with the wrong checksum by mistake.  Did that
 317 three times in the begin before I remembered my mistake.</p>
 318
 319 <p>So, if you are a Debian Developer and got some spare time, perhaps
 320 considering migrating some orphaned packages to git?</p>
 321
 322 <p>As usual, if you use Bitcoin and want to show your support of my
 323 activities, please send Bitcoin donations to my address
 324 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 325 </div>
 326       <div class="tags">
 327
 328
 329         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 330
 331
 332       </div>
 333     </div>
 334     <div class="padding"></div>
 335
 336     <div class="entry">
 337       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html">Plain text accounting file from your bitcoin transactions</a></div>
 338       <div class="date"> 7th March 2024</div>
 339       <div class="body"><p>A while back I wrote a small script to extract the Bitcoin
 340 transactions in a wallet in the
 341 <ahref="https://plaintextaccounting.org/">ledger plain text accounting
 342 format</a>.  The last few days I spent some time to get it working
 343 better with more special cases.  In case it can be useful for others,
 344 here is a copy:</p>
 345
 346 <p><blockquote><pre>
 347 #!/usr/bin/python3
 348 #  -*- coding: utf-8 -*-
 349 #  Copyright (c) 2023-2024 Petter Reinholdtsen
 350
 351 from decimal import Decimal
 352 import json
 353 import subprocess
 354 import time
 355
 356 import numpy
 357
 358 def format_float(num):
 359     return numpy.format_float_positional(num, trim='-')
 360
 361 accounts = {
 362     u'amount' : 'Assets:BTC:main',
 363 }
 364
 365 addresses = {
 366     '<some address>' : 'Assets:bankkonto',
 367     '<some address>' : 'Assets:bankkonto',
 368 }
 369
 370 def exec_json(cmd):
 371     proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
 372     j = json.loads(proc.communicate()[0], parse_float=Decimal)
 373     return j
 374
 375 def list_txs():
 376     # get all transactions for all accounts / addresses
 377     c = 0
 378     txs = []
 379     txidfee = {}
 380     limit=100000
 381     cmd = ['bitcoin-cli', 'listtransactions', '*', str(limit)]
 382     if True:
 383         txs.extend(exec_json(cmd))
 384     else:
 385         # Useful for debugging
 386         with open('transactions.json') as f:
 387             txs.extend(json.load(f, parse_float=Decimal))
 388     #print txs
 389     for tx in sorted(txs, key=lambda a: a['time']):
 390 #        print tx['category']
 391         if 'abandoned' in tx and tx['abandoned']:
 392             continue
 393         if 'confirmations' in tx and 0 >= tx['confirmations']:
 394             continue
 395         when = time.strftime('%Y-%m-%d %H:%M', time.localtime(tx['time']))
 396         if 'message' in tx:
 397             desc = tx['message']
 398         elif 'comment' in tx:
 399             desc = tx['comment']
 400         elif 'label' in tx:
 401             desc = tx['label']
 402         else:
 403             desc = 'n/a'
 404         print("%s %s" % (when, desc))
 405         if 'address' in tx:
 406             print("  ; to bitcoin address %s" % tx['address'])
 407         else:
 408             print("  ; missing address in transaction, txid=%s" % tx['txid'])
 409         print(f"  ; amount={tx['amount']}")
 410         if 'fee'in tx:
 411             print(f"  ; fee={tx['fee']}")
 412         for f in accounts.keys():
 413             if f in tx and Decimal(0) != tx[f]:
 414                 amount = tx[f]
 415                 print("  %-20s   %s BTC" % (accounts[f], format_float(amount)))
 416         if 'fee' in tx and Decimal(0) != tx['fee']:
 417             # Make sure to list fee used in several transactions only once.
 418             if 'fee' in tx and tx['txid'] in txidfee \
 419                and tx['fee'] == txidfee[tx['txid']]:
 420                 True
 421             else:
 422                 fee = tx['fee']
 423                 print("  %-20s   %s BTC" % (accounts['amount'], format_float(fee)))
 424                 print("  %-20s   %s BTC" % ('Expences:BTC-fee', format_float(-fee)))
 425                 txidfee[tx['txid']] = tx['fee']
 426
 427         if 'address' in tx and tx['address'] in addresses:
 428             print("  %s" % addresses[tx['address']])
 429         else:
 430             if 'generate' == tx['category']:
 431                 print("  Income:BTC-mining")
 432             else:
 433                 if amount < Decimal(0):
 434                     print(f"  Assets:unknown:sent:update-script-addr-{tx['address']}")
 435                 else:
 436                     print(f"  Assets:unknown:received:update-script-addr-{tx['address']}")
 437
 438         print()
 439         c = c + 1
 440     print("# Found %d transactions" % c)
 441     if limit == c:
 442         print(f"# Warning: Limit {limit} reached, consider increasing limit.")
 443
 444 def main():
 445     list_txs()
 446
 447 main()
 448 </pre></blockquote></p>
 449
 450 <p>It is more of a proof of concept, and I do not expect it to handle
 451 all edge cases, but it worked for me, and perhaps you can find it
 452 useful too.</p>
 453
 454 <p>To get a more interesting result, it is useful to map accounts sent
 455 to or received from to accounting accounts, using the
 456 <tt>addresses</tt> hash.  As these will be very context dependent, I
 457 leave out my list to allow each user to fill out their own list of
 458 accounts.  Out of the box, 'ledger reg BTC:main' should be able to
 459 show the amount of BTCs present in the wallet at any given time in the
 460 past.  For other and more valuable analysis, a account plan need to be
 461 set up in the <tt>addresses</tt> hash.  Here is an example
 462 transaction:</p>
 463
 464 <p><blockquote><pre>
 465 2024-03-07 17:00 Donated to good cause
 466     Assets:BTC:main                           -0.1 BTC
 467     Assets:BTC:main                       -0.00001 BTC
 468     Expences:BTC-fee                       0.00001 BTC
 469     Expences:donations                         0.1 BTC
 470 </pre></blockquote></p>
 471
 472 <p>It need a running Bitcoin Core daemon running, as it connect to it
 473 using <tt>bitcoin-cli listtransactions * 100000</tt> to extract the
 474 transactions listed in the Wallet.</p>
 475
 476 <p>As usual, if you use Bitcoin and want to show your support of my
 477 activities, please send Bitcoin donations to my address
 478 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 479 </div>
 480       <div class="tags">
 481
 482
 483         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 484
 485
 486       </div>
 487     </div>
 488     <div class="padding"></div>
 489
 490     <div class="entry">
 491       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html">RAID status from LSI Megaraid controllers using free software</a></div>
 492       <div class="date"> 3rd March 2024</div>
 493       <div class="body"><p>The last few days I have revisited RAID setup using the LSI
 494 Megaraid controller.  These are a family of controllers called PERC by
 495 Dell, and is present in several old PowerEdge servers, and I recently
 496 got my hands on one of these.  I had forgotten how to handle this RAID
 497 controller in Debian, so I had to take a peek in the
 498 <a href="https://wiki.debian.org/LinuxRaidForAdmins">Debian wiki page
 499 "Linux and Hardware RAID: an administrator's summary"</a> to remember
 500 what kind of software is available to configure and monitor the disks
 501 and controller.  I prefer Free Software alternatives to proprietary
 502 tools, as the later tend to fall into disarray once the manufacturer
 503 loose interest, and often do not work with newer Linux Distributions.
 504 Sadly there is no free software tool to configure the RAID setup, only
 505 to monitor it. RAID can provide improved reliability and resilience in
 506 a storage solution, but only if it is being regularly checked and any
 507 broken disks are being replaced in time.  I thus want to ensure some
 508 automatic monitoring is available.</p>
 509
 510 <p>In the discovery process, I came across a old free software tool to
 511 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
 512 surprise is not present in debian.  To help change that I created a
 513 <a href="https://bugs.debian.org/1065322">request for packaging of the
 514 megactl package</a>, and tried to track down a usable version.
 515 <a href="https://sourceforge.net/p/megactl/">The original project
 516 site</a> is on Sourceforge, but as far as I can tell that project has
 517 been dead for more than 15 years.  I managed to find a
 518 <a href="https://github.com/hmage/megactl">more recent fork on
 519 github</a> from user hmage, but it is unclear to me if this is still
 520 being maintained.  It has not seen much improvements since 2016.  A
 521 <a href="https://github.com/namiltd/megactl">more up to date
 522 edition</a> is a git fork from the original github fork by user
 523 namiltd, and this newer fork seem a lot more promising.  The owner of
 524 this github repository has replied to change proposals within hours,
 525 and had already added some improvements and support for more hardware.
 526 Sadly he is reluctant to commit to maintaining the tool and stated in
 527 <a href="https://github.com/namiltd/megactl/pull/1">my first pull
 528 request</A> that he think a new release should be made based on the
 529 git repository owned by hmage.  I perfectly understand this
 530 reluctance, as I feel the same about maintaining yet another package
 531 in Debian when I barely have time to take care of the ones I already
 532 maintain, but do not really have high hopes that hmage will have time
 533 to spend on it and hope namiltd will change his mind.</p>
 534
 535 <p>In any case, I created
 536 <a href="https://salsa.debian.org/debian/megactl">a draft package</a>
 537 based on the namiltd edition and put it under the debian group on
 538 salsa.debian.org.  If you own a Dell PowerEdge server with one of the
 539 PERC controllers, or any other RAID controller using the megaraid or
 540 megaraid_sas Linux kernel modules, you might want to check it out.  If
 541 enough people are interested, perhaps the package will make it into
 542 the Debian archive.</p>
 543
 544 <p>There are two tools provided, megactl for the megaraid Linux kernel
 545 module, and megasasctl for the megaraid_sas Linux kernel module. The
 546 simple output from the command on one of my machines look like this
 547 (yes, I know some of the disks have problems. :).</p>
 548
 549 <pre>
 550 # megasasctl
 551 a0       PERC H730 Mini           encl:1 ldrv:2  batt:good
 552 a0d0       558GiB RAID 1   1x2  optimal
 553 a0d1      3067GiB RAID 0   1x11 optimal
 554 a0e32s0     558GiB  a0d0  online   errs: media:0  other:19
 555 a0e32s1     279GiB  a0d1  online
 556 a0e32s2     279GiB  a0d1  online
 557 a0e32s3     279GiB  a0d1  online
 558 a0e32s4     279GiB  a0d1  online
 559 a0e32s5     279GiB  a0d1  online
 560 a0e32s6     279GiB  a0d1  online
 561 a0e32s8     558GiB  a0d0  online   errs: media:0  other:17
 562 a0e32s9     279GiB  a0d1  online
 563 a0e32s10    279GiB  a0d1  online
 564 a0e32s11    279GiB  a0d1  online
 565 a0e32s12    279GiB  a0d1  online
 566 a0e32s13    279GiB  a0d1  online
 567
 568 #
 569 </pre>
 570
 571 <p>In addition to displaying a simple status report, it can also test
 572 individual drives and print the various event logs.  Perhaps you too
 573 find it useful?</p>
 574
 575 <p>In the packaging process I provided some patches upstream to
 576 improve installation and ensure
 577 <ahref="https://github.com/namiltd/megactl/pull/2">a Appstream
 578 metainfo file is provided</a> to list all supported HW, to allow
 579 <a href="https://tracker.debian.org/isenkram">isenkram</a> to propose
 580 the package on all servers with a relevant PCI card.</p>
 581
 582 <p>As usual, if you use Bitcoin and want to show your support of my
 583 activities, please send Bitcoin donations to my address
 584 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 585
 586 </div>
 587       <div class="tags">
 588
 589
 590         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
 591
 592
 593       </div>
 594     </div>
 595     <div class="padding"></div>
 596
 597     <div class="entry">
 598       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html">Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</a></div>
 599       <div class="date">27th February 2024</div>
 600       <div class="body"><p>Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
 601 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
 602 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
 603 2024-03-12.  Seminaret finner sted ved Oslo byarkiv.  Vi håper å få
 604 til videostrømming via Internett av presentasjoner og paneldiskusjon.
 605 Oppdatert program og lenker til påmeldingsskjema er
 606 <a href="https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html">tilgjengelig
 607 fra Nikita-prosjektet</a>.  Arrangementet er gratis.
 608
 609 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 610 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 611 til min adresse
 612 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
 613 betaling med bitcoin er ikke anonymt. :)</p>
 614 </div>
 615       <div class="tags">
 616
 617
 618         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 619
 620
 621       </div>
 622     </div>
 623     <div class="padding"></div>
 624
 625     <div class="entry">
 626       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html">Welcome out of prison, Mickey, hope you find some freedom!</a></div>
 627       <div class="date"> 1st January 2024</div>
 628       <div class="body"><p align="center"><img src="https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg"/></p>
 629
 630 <p>Today, the animation figure Mickey Mouse finally was released from
 631 the corporate copyright prison, as the 1928 movie
 632 <a href="https://en.wikipedia.org/wiki/Steamboat_Willie">Steamboat
 633 Willie</a> entered the public domain in USA.  This movie was the first
 634 public appearance of Mickey Mouse.  Sadly the figure is still on
 635 probation, thanks to trademark laws and a the Disney corporations
 636 powerful pack of lawyers, as described in the 2017 article
 637 in <a href="https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/">"How
 638 Mickey Mouse Evades the Public Domain"</a> from Priceonomics.  On the
 639 positive side, the primary driver for repeated extentions of the
 640 duration of copyright has been Disney thanks to Mickey Mouse and the
 641 2028 movie, and as it now in the public domain I hope it will cause
 642 less urge to extend the already unreasonable long copyright
 643 duration.</p>
 644
 645 <p>The first book I published, the 2004 book <a
 646 href="https://free-culture.cc/">"Free Culture" by Lawrence Lessig</a>,
 647 published 2015 in
 648 <a href="https://people.skolelinux.org/pere/publisher/#frikultur">English,
 649 French and Norwegian Bokmål</a>, touch on the story of Disney pushed
 650 for extending the copyright duration in USA.  It is a great book
 651 explaining problems with the current copyright regime and why we need
 652 Creative Commons movement, and I strongly recommend everyone to read
 653 it.</p>
 654
 655 <p>This movie (with
 656 <a href="https://www.imdb.com/title/tt0019422/">IMDB ID tt0019422</a>)
 657 is now available from the Internet Archive.  Two copies have been
 658 uploaded so far, one uploaded
 659 <a href="https://archive.org/details/SteamboatWillie">2015-11-04</a>
 660 (<a href="https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent">torrent</a>)
 661 and the other
 662 <a href="https://archive.org/details/steamboat-willie-mickey">2023-01-01</a>
 663 (<a href="https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent">torrent</a>) - see
 664 <a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC
 665 bittorrent plugin</a> for streaming the video using the torrent link.
 666 I am very happy to see
 667 <a href="https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html">the
 668 number of public domain movies</a> increasing.  I look forward to
 669 when those are the majority.  Perhaps it will reduce the urge of the
 670 copyright industry to control its customers.</p>
 671
 672 <p>A more
 673 <a href="https://publicdomainreview.org/features/entering-the-public-domain/2024/">comprehensive
 674 list of works entering the public domain in 2024</a> is available from
 675 the Public Domain Review.</p>
 676
 677 <p>As usual, if you use Bitcoin and want to show your support of my
 678 activities, please send Bitcoin donations to my address
 679 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 680 </div>
 681       <div class="tags">
 682
 683
 684         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
 685
 686
 687       </div>
 688     </div>
 689     <div class="padding"></div>
 690
 691     <div class="entry">
 692       <div class="title"><a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC bittorrent plugin still going strong, new upload 2.14-4</a></div>
 693       <div class="date">31st December 2023</div>
 694       <div class="body"><p>The other day I uploaded a new version of
 695 <a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
 696 bittorrent plugin</a> to Debian, version 2.14-4, to fix a few
 697 packaging issues.  This plugin extend VLC allowing it to stream videos
 698 directly from a bittorrent source using both torrent files and magnet
 699 links, as easy as using a HTTP or local file source.  I believe such
 700 protocol support is a vital feature in VLC, allowing efficient
 701 streaming from sources such at the 11 million movies in
 702 <a href="https://archive.org/">the Internet Archive</a>.  Bittorrent is
 703 one of the most efficient content distribution protocols on the
 704 Internet, without centralised control, and should be used more.</p>
 705
 706 <p>The new version is now both in Debian Unstable and Testing, as well
 707 as Ubuntu.  While looking after the package, I decided to ask the VLC
 708 upstream community if there was any hope to get Bittorrent support
 709 into the official VLC program, and was very happy to learn that
 710 someone is already working on it.  I hope we can see some fruits of
 711 that labour next year, but do not hold my breath.  In the mean time we
 712 can use the plugin, which is already
 713 <a href="https://qa.debian.org/popcon.php?package=vlc-plugin-bittorrent">installed
 714 by 0.23 percent of the Debian population</a> according to
 715 popularity-contest.  It could use a new upstream release, and I hope
 716 the upstream developer soon find time to polish it even more.</p>
 717
 718 <p>It is worth noting that the plugin store the downloaded files in
 719 <tt>~/Downloads/vlc-bittorrent/</tt>, which can quickly fill up the
 720 user home directory during use.  Users of the plugin should keep an
 721 eye with disk usage when streaming a bittorrent source.</p>
 722
 723 <p>As usual, if you use Bitcoin and want to show your support of my
 724 activities, please send Bitcoin donations to my address
 725 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 726 </div>
 727       <div class="tags">
 728
 729
 730         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 731
 732
 733       </div>
 734     </div>
 735     <div class="padding"></div>
 736
 737     <div class="entry">
 738       <div class="title"><a href="https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html">«Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra depotet» i tidsskriftet Aksess</a></div>
 739       <div class="date">15th November 2023</div>
 740       <div class="body"><p>For noen uker siden skrev en kamerat og meg
 741 <a href="https://www.aksess-tidsskrift.no/fordypning/175530">en
 742 artikkel om tegnsett</a> i
 743 <a href="https://www.aksess-tidsskrift.no/">arkivtidsskriftet
 744 Aksess</a> både på web og i papirutgave nr. 3 2023.  Her er det som
 745 nettopp ble publisert.</p>
 746
 747 <blockquote>
 748
 749 <p><strong>Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra
 750 depotet</strong></p>
 751
 752 <p>av Thomas Sødring og Petter Reinholdtsen</p>
 753
 754 <p>De færreste av oss tenker over hva som skjer dypere i datamaskinen
 755 mens vi sitter der og skriver noe på tastaturet. Når du trykker på
 756 tasten «Å», så vises bokstaven Å. Men noen ganger blir det
 757 feil. Hvorfor det – og hva er viktig å være klar over i
 758 arkivsammenheng?</p>
 759
 760 <p>Dersom bokstaver tolkes forskjellig mellom systemer, blir det fort
 761 rot, dette kalles mojibake blant kjennere, etter det japanske
 762 uttrykket for tegnomforming. Det er en lang historie her som tidvis
 763 har vært preget av rot.  Noen husker kanskje tilbake til en tid der
 764 bokstavene æ, ø og å ofte var ødelagt i e-poster – et klassisk
 765 eksempel på tegnsettproblemstilling.</p>
 766
 767 <p id="tegnsett_access_nå_og_før"><strong>«Nå» og «før»</strong></p>
 768
 769 <p>Tid er et skjult problem for depot fordi vi danner dokumentasjon i
 770 en kontekst som er preget av å være «nå».  Vår forståelse av verden og
 771 bruken av teknologi er utgangspunktet for denne konteksten. Tenk selv
 772 hvordan verden har utviklet seg de siste 20 årene, hva samfunnet er
 773 opptatt av, og hvordan vi bruker teknologi i hverdagen. Tid er et
 774 skjult problem fordi når vi trekker dokumentasjon ut av systemer og
 775 deponerer for langtidsbevaring, er konteksten til materialet «nå», men
 776 verden går videre. Ettersom teknologien og måten vi bruker den på,
 777 utvikler seg, blir «nå» til «før», og dokumentasjonen befinner seg
 778 snart i en «før»-kontekst.</p>
 779
 780 <p>Dette med «før» og «nå» i forhold til dokumentasjonens kontekst er
 781 noe vi er veldig lite bevisste på, men det er en problemstilling
 782 depotarkivene eier og forvalter.  En av disse utfordringene er hvorfor
 783 «Ø» ikke nødvendigvis er det samme som «Ø», og hvorfor det i det hele
 784 tatt gir mening å si noe sånt. Vi snakker her om noe som heter
 785 tegnsett, som er en avtalt måte å representere bokstaver, tall og
 786 andre symboler på slik at vi på en feilfri måte kan utveksle tekst
 787 mellom datasystemer.</p>
 788
 789 <p>Tegnsettproblemstillingen er satt sammen av fire fasetter;
 790 repertoar, representasjon, koding og uttegning.</p>
 791
 792 <p id="tegnsett_access_repertoarer"><strong>Repertoarer</strong></p>
 793
 794 <p>Repertoar er en samling med tegn og symboler som kan
 795 representeres. Tenk norsk alfabet eller japanske piktogrammer, men
 796 også matematiske og elektroniske symboler. Bokstaven «stor a» kan være
 797 en oppføring i et slikt repertoar. For å kunne brukes i en datamaskin
 798 trenger hver oppføring i et slikt repertoar en representasjon, hvilket
 799 i datamaskinsammenheng betyr at det tilordnes et tall. Tallet kan
 800 lagres på ulike vis i en eller flere kodingsformater. For eksempel kan
 801 en skrive tallet ti som både 10, X og A, i henholdsvis
 802 titallssystemet, romertallssystemet og sekstentallssystemet.</p>
 803
 804 <p>Hvis en skal kunne lese inn filer og vite hvilket tall og hvilken
 805 representasjon og instans i et repertoar det er snakk om, så må en
 806 vite hvordan tallet er kodet. Sist, men ikke minst, for å kunne bruke
 807 symbolet til noe må det kunne være kjent hvordan det skal se ut eller
 808 tegnes på ark. Det finnes utallige skrifttyper med norske bokstaver,
 809 alle litt forskjellige, og skal en kunne tegne en stor A på skjermen,
 810 så må datamaskinen vite hva den skal tegne. Skrifttyper inneholder
 811 informasjon om hvordan ulike tall skal tegnes. De inneholder ikke
 812 alltid alle symbolene som er brukt i en tekst, hvilket gjør at ikke
 813 alle forståtte tegn vil kunne vises på skjerm eller ark.</p>
 814
 815 <p>Hver av disse fasettene må være avklart for å kunne ta vare på og vise
 816 frem tekst med en datamaskin. Kombinasjon av repertoar, representasjon
 817 og koding er det en kaller et tegnsett. Kombinasjonen av
 818 representasjon og uttegning kalles en skrifttype. De fleste
 819 skrifttyper har også informasjon om repertoar, men det finnes
 820 skrifttyper som kun kobler mellom tallkode og uttegning, uten å
 821 fortelle noe om hvordan tallkodene egentlig skal tolkes.</p>
 822
 823 <p id="tegnsett_access_fra_ascii_til_iso_8859"><strong>Fra ASCII til ISO-8859</strong></p>
 824
 825 <p>Vi begynner historien med ASCII (American Standard Code for
 826 Information Interchange) som har en historie som spores tilbake til
 827 1963. Utgangspunktet til ASCII var at det kunne kode opp til 128
 828 forskjellige symboler i vanlig bruk i USA. De visuelle symbolene i
 829 ASCII er de små og store bokstavene (a til z og A til Z), tall (0 til
 830 9) og tegnsettingssymboler (for eksempel semikolon, komma og
 831 punktum). ASCII har også noen usynlige symboler som ble brukt for
 832 bl.a. kommunikasjon. Før ASCII var det for eksempel teleks-tegnsett
 833 med plass til bare 32 tegn og EBCDIC med plass til 256 tegn, alle med
 834 en helt annen rekkefølge på symbolene enn ASCII, men de har vært lite
 835 brukt de siste femti årene. Et eksempel på noen utvalgte symboler i
 836 repertoaret til ASCII vises i tabell 1.</p>
 837
 838 <table align="center" width="50%">
 839
 840 <caption>Tabell 1. Eksempel på utvalgte symboler hentet fra
 841 ASCII-tegnsettet. Kolonnen «Binær» viser symbolets verdi i
 842 totallssystemet (1 og 0 tall), mens kolonnen «Desimal» viser symbolets
 843 verdi i titallssystemet.</caption>
 844
 845 <tbody>
 846 <tr>
 847 <th>Grafisk</th>
 848 <th>Binær</th>
 849 <th>Desimal</th>
 850 </tr>
 851 <tr>
 852 <td>A</td>
 853 <td>1000001</td>
 854 <td align="right">65</td>
 855 </tr>
 856 <tr>
 857 <td>M</td>
 858 <td>1001101</td>
 859 <td align="right">77</td>
 860 </tr>
 861 <tr>
 862 <td>Z</td>
 863 <td>1011010</td>
 864 <td align="right">90</td>
 865 </tr>
 866 <tr>
 867 <td>a</td>
 868 <td>1100001</td>
 869 <td align="right">97</td>
 870 </tr>
 871 <tr>
 872 <td>m</td>
 873 <td>1101101</td>
 874 <td align="right">109</td>
 875 </tr>
 876 <tr>
 877 <td>z</td>
 878 <td>1111010</td>
 879 <td align="right">122</td>
 880 </tr>
 881 <tr>
 882 <td>0</td>
 883 <td>0110000</td>
 884 <td align="right">48</td>
 885 </tr>
 886 <tr>
 887 <td>9</td>
 888 <td>0111001</td>
 889 <td align="right">58</td>
 890 </tr>
 891 <tr>
 892 <td>;</td>
 893 <td>0111011</td>
 894 <td align="right">59</td>
 895 </tr>
 896 </tbody>
 897 </table>
 898
 899 <p>Det opprinnelige ASCII-tegnsettet ble også omtalt som ASCII-7 og
 900 brukte 7 bits (0 og 1) for å representere symboler. Datamaskiner er
 901 ofte konfigurert til å jobbe med enheter der bits er gruppert som 4
 902 eller 8 bits . Det lå en mulighet i å ta i bruk bit åtte. En slik
 903 endring ville gjøre det mulig for datamaskiner å øke antall symboler
 904 de kunne representere, noe som ga en økning fra 128 forskjellige
 905 symboler til 256 forskjellige symboler. Det ble åpnet for å innlemme
 906 de nordiske bokstavene sammen med ASCII, og dette ble etter hvert
 907 standardisert som ISO-8859-1. Tabell 2 viser deler av ISO-8859-1 som
 908 støtter de norske bokstavene.</p>
 909
 910 <p>Det sier seg selv at muligheten til å representere inntil 256 symboler
 911 ikke holder når vi snakker om en global verden, og det ble gjort et
 912 standardiseringsløp som tok utgangspunkt i ASCII-7 med en utvidelse
 913 til å bruke den åttende biten for ulike språkgrupper. Denne standarden
 914 heter ISO-8859 og er inndelt i opptil 16 varianter, altså fra
 915 ISO-8859-1 til ISO-8859-16.</p>
 916
 917 <table align="center" width="50%">
 918
 919 <caption>Tabell 2. Koding av de norske symbolene slik de er definert i
 920 ISO-8859-1 tegnsettet.</caption>
 921
 922 <tbody>
 923 <tr>
 924 <th>Grafisk</th>
 925 <th>Binær</th>
 926 <th>Desimal</th>
 927 </tr>
 928 <tr>
 929 <td>Æ</td>
 930 <td>11000110</td>
 931 <td align="right">198</td>
 932 </tr>
 933 <tr>
 934 <td>Ø</td>
 935 <td>11011000</td>
 936 <td align="right">216</td>
 937 </tr>
 938 <tr>
 939 <td>Å</td>
 940 <td>11000101</td>
 941 <td align="right">197</td>
 942 </tr>
 943 <tr>
 944 <td>æ</td>
 945 <td>11100110</td>
 946 <td align="right">230</td>
 947 </tr>
 948 <tr>
 949 <td>ø</td>
 950 <td>11111000</td>
 951 <td align="right">248</td>
 952 </tr>
 953 <tr>
 954 <td>å</td>
 955 <td>11100101</td>
 956 <td align="right">229</td>
 957 </tr>
 958 </tbody>
 959 </table>
 960
 961 <p>Norske tegn er definert i ISO-8859-1, som også omtales som Latin 1, de
 962 fleste samiske tegn er definert i ISO-8859-4 (Latin 4) mens tilgang
 963 til €-symbolet kom med ISO-8859-15 (Latin 9). ISO-8859-15 er en
 964 revisjon av ISO-8859-1 som fjerner noen lite brukte symboler og
 965 erstatter bokstaver som er mer brukt, og introduserer €-symbolet.  Det
 966 er viktig å merke at alle ISO-8859-variantene har overlapp med
 967 ASCII-7, noe som ga samvirke med de engelskspråklige landene som ikke
 968 trengte å gjøre noe. Det innebærer også at de første 128 verdiene i
 969 ISO-8859-variantene representerer de samme symbolene. Det er først når
 970 du kommer til tolkningen av de resterende 128 verdiene med nummer 128
 971 til 255, at det oppsto tolkningsutfordringer mellom
 972 ISO-8859-variantene.</p>
 973
 974 <p>ISO-8859-verdenen fungerte godt så lenge tegnsettet som ble brukt når
 975 innhold ble skapt, også ble brukt når innhold ble gjengitt og du ikke
 976 trengte å kombinere innhold fra forskjellige tegnsett i samme
 977 dokument.  Utfordringen med bruken av ISO-8859-variantene ble raskt
 978 tydelig i en mer globalisert verden med utveksling av tekst på tvers
 979 av landegrenser der tekstlig innhold i dokumenter, e-poster og
 980 websider kunne bli skrevet med ett tegnsett og gjengitt med et annet
 981 tegnsett.</p>
 982
 983 <table align="center" width="60%">
 984
 985 <caption>Tabell 3. Viser tolkning av verdiene som er tilegnet de
 986 norske symbolene i ISO-8859-1 i de andre ISO 8859-variatene. Merk
 987 ISO-8859-12 ikke finnes da arbeidet ble avsluttet.<sup>[<a id="tegnsett_access_footnoteref_1" href="#tegnsett_access_footnotedef_1" title="View footnote.">1</a>]</sup></caption>
 988
 989 <tbody>
 990 <tr>
 991 <th>Binærverdi</th>
 992 <th>1</th>
 993 <th>2</th>
 994 <th>3</th>
 995 <th>4</th>
 996 <th>5</th>
 997 <th>6</th>
 998 <th>7</th>
 999 <th>8</th>
1000 <th>9</th>
1001 <th>10</th>
1002 <th>11</th>
1003 <th>13</th>
1004 <th>14</th>
1005 <th>15</th>
1006 <th>16</th>
1007 </tr>
1008 <tr>
1009 <td>11000110</td>
1010 <td>Æ</td>
1011 <td>Ć</td>
1012 <td>Ĉ</td>
1013 <td>Æ</td>
1014 <td>Ц</td>
1015 <td>ئ</td>
1016 <td>Ζ</td>
1017 <td></td>
1018 <td>Æ</td>
1019 <td>Æ</td>
1020 <td>ฦ</td>
1021 <td>Ę</td>
1022 <td>Æ</td>
1023 <td>Æ</td>
1024 <td>Æ</td>
1025 </tr>
1026 <tr>
1027 <td>11011000</td>
1028 <td>Ø</td>
1029 <td>Ř</td>
1030 <td>Ĝ</td>
1031 <td>Ø</td>
1032 <td>и</td>
1033 <td>ظ</td>
1034 <td>Ψ</td>
1035 <td></td>
1036 <td>Ø</td>
1037 <td>Ø</td>
1038 <td>ุ</td>
1039 <td>Ų</td>
1040 <td>Ø</td>
1041 <td>Ø</td>
1042 <td>Ű</td>
1043 </tr>
1044 <tr>
1045 <td>11000101</td>
1046 <td>Å</td>
1047 <td>Ĺ</td>
1048 <td>Ċ</td>
1049 <td>Å</td>
1050 <td>Х</td>
1051 <td>إ</td>
1052 <td>Ε</td>
1053 <td></td>
1054 <td>Å</td>
1055 <td>Å</td>
1056 <td>ล</td>
1057 <td>Å</td>
1058 <td>Å</td>
1059 <td>Å</td>
1060 <td>Ć</td>
1061 </tr>
1062 <tr>
1063 <td>11100110</td>
1064 <td>æ</td>
1065 <td>ć</td>
1066 <td>ĉ</td>
1067 <td>æ</td>
1068 <td>ц</td>
1069 <td>ن</td>
1070 <td>ζ</td>
1071 <td>ז</td>
1072 <td>æ</td>
1073 <td>æ</td>
1074 <td>ๆ</td>
1075 <td>ę</td>
1076 <td>æ</td>
1077 <td>æ</td>
1078 <td>v</td>
1079 </tr>
1080 <tr>
1081 <td>11111000</td>
1082 <td>ø</td>
1083 <td>ř</td>
1084 <td>ĝ</td>
1085 <td>ø</td>
1086 <td>ј</td>
1087 <td></td>
1088 <td>ψ</td>
1089 <td>ר</td>
1090 <td>ø</td>
1091 <td>ø</td>
1092 <td>๘</td>
1093 <td>ų</td>
1094 <td>ø</td>
1095 <td>ø</td>
1096 <td>ű</td>
1097 </tr>
1098 <tr>
1099 <td>11100101</td>
1100 <td>å</td>
1101 <td>ĺ</td>
1102 <td>ċ</td>
1103 <td>å</td>
1104 <td>х</td>
1105 <td>م</td>
1106 <td>ε</td>
1107 <td>ו</td>
1108 <td>å</td>
1109 <td>å</td>
1110 <td>ๅ</td>
1111 <td>å</td>
1112 <td>å</td>
1113 <td>å</td>
1114 <td>ć</td>
1115 </tr>
1116 </tbody>
1117 </table>
1118
1119 <p>Denne problemstillingen er illustrert i tabell 3, der vi ser verdiene
1120 tilegnet de norske symbolene i ISO-8859-1 i kolonne «1». I de øvrige
1121 kolonnene ser vi hvilket symbol verdien får i de andre
1122 ISO-8859-variantene. Tar vi utgangspunkt i tabell 3, kan vi se at
1123 ordet lærlingspørsmål gjengitt med ISO-8859-2 (kolonne 2) blir
1124 lćrlingspřrsmĺl, mens det blir lζrlingspψrsmεl med ISO- 8859-7
1125 (kolonne 7). Med ISO-8859-2 blir «æ» til «ć», «ø» til «ř» og «å» til
1126  «ĺ». I ISO-8859-7 blir «æ» til «ζ», «ø» til «ψ», mens «å» blir «ε».</p>
1127
1128 <p>Det er egentlig ingen utfordring med dette så lenge du vet hvilket
1129 tegnsett innholdet ditt er representert med, og det ikke har skjedd
1130 omforminger som du ikke er klar over. Det er det siste som er
1131 problematisk, spesielt de datasystemene som har vært i bruk de siste
1132 20 årene, som ikke har noe innebygd funksjonalitet for å forvalte
1133 tegnsettproblematikken. Et godt eksempel på dette er
1134 Microsoft-tegnsettet Windows-1252, som ble forvekslet som 100 %
1135 kompatibel med ISO-8859-1, men hadde byttet ut plassene fra 127 til
1136 159. Historisk vil det finnes en del variasjon i hvilket tegnsett som
1137 har vært i bruk, og hvor vellykket konvertering mellom tegnsett har
1138 vært.</p>
1139
1140 <p id="tegnsett_access_unicode_som_løsning"><strong>Unicode som løsning</strong></p>
1141
1142 <p>Tegnsettforvirring ble etter hvert et irritasjonsmoment og
1143 samvirkeproblem. Ofte fikk man en e-post der æøå var erstattet av rare
1144 symboler fordi e-posten hadde vært innom et eller annet datasystem som
1145 ikke brukte samme tegnsett.</p>
1146
1147 <p>For å løse dette samvirkeproblemet for tegnsett ble det startet et
1148 arbeid og en ny standard så dagens lys etter hvert. Denne standarden
1149 fikk navnet Unicode (ISO/ IEC 10646) og skulle resultere i et tegnsett
1150 som alle skulle være enige om. Unicode er et repertoar og en
1151 representasjon, dvs. navngivning og tilordning av tallverdi til alle
1152 symboler i bruk i verden i dag.  Oppføringer i Unicode skrives gjerne
1153 U+XXXX der XXXX er tallkoden i sekstentallssystemet som oppføringen
1154 har i Unicode-katalogen. Her finner vi tegn brukt av både levende og
1155 døde språk, konstruerte språk, tekniske symboler, morsomme tegninger
1156 (såkalte emojier) og tegn ingen vet hva betyr eller skal brukes
1157 til. Et morsomt eksempel er i nettartikkelen: U+237C ⍼ RIGHT ANGLE
1158 WITH DOWNWARDS ZIGZAG ARROW, av Jonathan Chan.<sup>[<a id="tegnsett_access_footnoteref_2" href="#tegnsett_access_footnotedef_2" title="View footnote.">2</a>]</sup></p>
1159
1160 <p>Sammen med Unicode kom det tre måter å kode disse tallene på; UTF-8,
1161 UTF-16 og UTF-32. Av datatekniske årsaker er UTF-8 mye brukt, spesielt
1162 når det gjelder utveksling av tekst over Internett, mens UTF-16 er
1163 brukt en del til tekstfiler lagret på Windows. En utfordring med
1164 Unicode og UTF-variantene er at disse gir flere måter å kode samme
1165 symbol på med en kombinasjonsmekanisme. Dette kan gi utfordringer ved
1166 søk, hvis en skal søke etter et ord som har ett eller flere symboler
1167 som kan skrives på ulikt vis, så er det ikke sikkert at søkesystemet
1168 vil finne alle forekomster. For eksempel kan bokstaven U+00F8 «Latin
1169 Small Letter O with Stroke» kodes som den tradisjonelle norske tegnet
1170 ø, men også som o kombinert med skråstrek U+0338. Begge deler er
1171 gyldig bruk av Unicode, selv om det er tradisjon for å foretrekke å
1172 «normalisere» kombinasjoner som enkelttegn der det er mulig, nettopp
1173 for å forenkle søk.</p>
1174
1175 <p id="tegnsett_access_bare_unicode_fremover"><strong>Bare Unicode fremover</strong></p>
1176
1177 <p>Forvaltningens bruk av tegnsett er regulert i Forskrift om
1178 IT-standarder i offentlig forvaltning<sup>[<a id="tegnsett_access_footnoteref_3" href="#tegnsett_access_footnotedef_3" title="View footnote.">3</a>]</sup>. Her står det: «Ved all
1179 utveksling av informasjon mellom forvaltningsorganer og fra
1180 forvaltningsorgan til innbyggere og næringsliv skal tegnsettstandarden
1181 ISO/IEC 10646 representert ved UTF8 benyttes.»  Det er forskjellige
1182 bruksområder til UTF-8, UTF-16 og UTF-32, men UTF-8 er kodingen vi
1183 kjenner mest til.  Det er flere grunner at UTF-8 «vant» konkurransen
1184 til å bli den utvalgte. Den kanskje viktigste er at UTF-8 er fullt
1185 samvirkende med ASCII-7, slik at den engelskspråklige delen av verden
1186 kunne rulle ut UTF-8 uten å merke noe forskjell. En tekstfil med kun
1187 ASCII-tekst vil være identisk på disken hvis den lagres som UTF-8 og
1188 ASCII. UTF-16 og UTF-32 byr på noen optimaliseringer som gjør dem
1189 relevant for spesifikke problemområder, men for det meste vil vi aldri
1190 oppleve disse standardene på nært hold i hverdagen. Det er uansett kun
1191 bruken av UTF-8 som er lovregulert i Norge.</p>
1192
1193 <p>Det er ikke slik at hele verden bruker ISO/IEC 10646 og UTF-8. Kina
1194 har egne standarder for tegnsett, mye brukt er GB 18030, som er
1195 Unicode med en annen koding enn UTF-8, mens Taiwan og andre asiatiske
1196 land gjerne bruker Big5 eller andre tegnsett.</p>
1197
1198 <p>UTF-8 er dominerende i Norge, men det er tidsperioder der forskjellige
1199 datasystemer utvekslet data i henhold til ISO-8859-1, ISO-8859-15,
1200 Windows-1252, Codepage 865 og ISO-646-60 / Codepage 1016 mens
1201 overgangen til UTF-8 pågikk. Det er ikke slik at et datasystem enkelt
1202 kan tvinges til å bruke et tegnsett, da det er flere lag i et
1203 datasystem som må settes opp til å bruke riktig tegnsett, og
1204 tegnsettproblemet fort oppstår når det er et eller annet i
1205 datasystemet som bruker feil tegnsett.</p>
1206
1207 <p>Et klassisk eksempel på problemet er en utveksling av tekst mellom to
1208 systemer der teksten i utgangspunktet er kodet i UTF-8, men går
1209 gjennom noe som er ISO-8859-1 underveis. Dette kan vises med at ordet
1210 «på» i et slik scenario ender opp som «pÃ¥». Det er mulig å spore
1211 dette tilbake til verdiene symbolene er tilordnet i tegnsettene. «på»
1212 blir til «pÃ¥» fordi «å» i UTF-8 er representert med U+C3AF, og dersom
1213 vi ser på hva disse verdiene representerer, ser vi at
1214 sekstentallssystemverdien C3 er 1100 0011 i totallssystemet og
1215 symbolet med dette tallet i ISO-8859-1 er Ã.</p>
1216
1217 <p>Vi ser det samme med sekstentallssystemverdien A5, som er 1010 0101 i
1218 totallssystemet, og tilsvarende symbol i ISO-8859-1 er ¥. Slik
1219 mojibake kan lett skje hvis «på» i utgangspunktet var representert med
1220 UTF-8, men ble behandlet med et system som bruker ISO-8859-1. Det er
1221 ingen automatikk i å fange opp slike ødeleggelser mens tekstlig
1222 innhold utveksles mellom datasystemer.</p>
1223
1224 <p>En utfordring for depotarkivene er at bruken av tegnsett ikke alltid
1225 har vært regulert, og at det kan finnes flere dokumentasjonssamlinger
1226 som er opprettet med varierende tegnsett før gjeldende forskrift
1227 inntraff – uten at det er mulig å avlede fra filene hvilket tegnsett
1228 som ble brukt. Et eksempel på dette er €-symbolet, som kom først etter
1229 at ISO-8859-1 var tatt i bruk. Det kan bli en utfordring for et
1230 depotarkiv, men så lenge det er kjent hvilket tegnsett var i bruk, så
1231 bør det gå bra.  Riksarkivarens
1232 forskrift<sup>[<a id="tegnsett_access_footnoteref_4" href="#tegnsett_access_footnotedef_4" title="View footnote.">4</a>]</sup>
1233 formaliserer dette ved å kreve følgende:</p>
1234
1235 <blockquote>
1236 <p>§ 5-11. Tegnsett i arkivuttrekk</p>
1237
1238 <ol>
1239   <li>Arkivuttrekk og medfølgende struktur- og innholdsbeskrivelser skal
1240       overføres som ren tekst i ukryptert form, og benytte godkjent
1241       tegnsett.</li>
1242
1243   <li>Godkjente tegnsett er:
1244     <ol>
1245       <li>Unicode UTF-8<br>
1246           (ISO/IEC 10646-1:2000 Annex D)</li>
1247       <li>ISO 8859-1:1998, Latin 1</li>
1248       <li>ISO 8859-4:1998, Latin 4 for samiske tegn.</li>
1249     </ol></li>
1250
1251   <li>Andre tegnsett aksepteres bare etter avtale med Arkivverket.</li>
1252 </ol>
1253 </blockquote>
1254
1255 <p id="tegnsett_access_ditt_ansvar"><strong>Ditt ansvar</strong></p>
1256
1257 <p>På mange måter burde ikke tegnsett være et problem i 2023, men sånn er
1258 det nok ikke. Land som har oppgradert til UTF-8 som primærtegnsett for
1259 utveksling av tekstlig innhold, begrenser problematikken betraktelig,
1260 men globalt sett så er tegnsettutfordringen ikke løst fordi ikke alle
1261 er enige om å bruke samme tegnsett.  Det kan være geopolitiske eller
1262 kulturelle hensyn som ligger til grunn for dette.</p>
1263
1264 <p>Det er uansett verdt å merke at selv om bruken av UTF-8 skulle bli
1265 100% utbredt, så er det et historisk perspektiv (ASCII-7,
1266 ISO-8859-variantene, UTF-8) her som gjør tegnsett til et problemområde
1267 arkivarene må forstå og håndtere.  Som danningsarkivar har du et
1268 ansvar for å vite hvilket tegnsett systemene og databasene dere
1269 forvalter, er i samsvar med. Det er noe IT-avdelingen din eller
1270 programvareleverandørene enkelt skal kunne svare på, og svaret skal
1271 være UTF-8 for alle nye systemer.</p>
1272
1273 <hr>
1274
1275 <p id="tegnsett_access_footnotedef_1"><a href="#tegnsett_access_footnoteref_1">1</a>. Tegnsettkilde <a href="https://en.wikipedia.org/wiki/ISO/IEC_8859">https://en.wikipedia.org/wiki/ISO/IEC_8859</a></p>
1276
1277 <p id="tegnsett_access_footnotedef_2"><a href="#tegnsett_access_footnoteref_2">2</a>. <a href="https://ionathan.ch/2022/04/09/angzarr.html">https://ionathan.ch/2022/04/09/angzarr.html</a></p>
1278
1279 <p id="tegnsett_access_footnotedef_3"><a href="#tegnsett_access_footnoteref_3">3</a>. <a href="https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78">https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78</a></p>
1280
1281 <p id="tegnsett_access_footnotedef_4"><a href="#tegnsett_access_footnoteref_4">4</a>. <a href="https://lovdata.no/forskrift/2017-12-19-2286/§5-11">https://lovdata.no/forskrift/2017-12-19-2286/§5-11</a></p>
1282
1283 </blockquote>
1284
1285 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i Norge.</p>
1286
1287 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1288 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1289 til min adresse
1290 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
1291 betaling med bitcoin er ikke anonymt. :)</p>
1292 </div>
1293       <div class="tags">
1294
1295
1296         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1297
1298
1299       </div>
1300     </div>
1301     <div class="padding"></div>
1302
1303     <p style="text-align: right;"><a href="index.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
1304     <div id="sidebar">
1305
1306
1307
1308 <h2>Archive</h2>
1309 <ul>
1310
1311 <li>2024
1312 <ul>
1313
1314 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/01/">January (1)</a></li>
1315
1316 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/02/">February (1)</a></li>
1317
1318 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/03/">March (2)</a></li>
1319
1320 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/04/">April (3)</a></li>
1321
1322 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/05/">May (1)</a></li>
1323
1324 </ul></li>
1325
1326 <li>2023
1327 <ul>
1328
1329 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
1330
1331 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
1332
1333 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/04/">April (2)</a></li>
1334
1335 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/05/">May (3)</a></li>
1336
1337 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/06/">June (1)</a></li>
1338
1339 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/08/">August (1)</a></li>
1340
1341 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/09/">September (1)</a></li>
1342
1343 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/10/">October (1)</a></li>
1344
1345 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/11/">November (4)</a></li>
1346
1347 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/12/">December (1)</a></li>
1348
1349 </ul></li>
1350
1351 <li>2022
1352 <ul>
1353
1354 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
1355
1356 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
1357
1358 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
1359
1360 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
1361
1362 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
1363
1364 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
1365
1366 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
1367
1368 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
1369
1370 </ul></li>
1371
1372 <li>2021
1373 <ul>
1374
1375 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
1376
1377 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
1378
1379 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
1380
1381 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
1382
1383 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
1384
1385 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
1386
1387 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
1388
1389 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
1390
1391 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
1392
1393 </ul></li>
1394
1395 <li>2020
1396 <ul>
1397
1398 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
1399
1400 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
1401
1402 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
1403
1404 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
1405
1406 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
1407
1408 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
1409
1410 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
1411
1412 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
1413
1414 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
1415
1416 </ul></li>
1417
1418 <li>2019
1419 <ul>
1420
1421 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
1422
1423 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
1424
1425 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
1426
1427 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
1428
1429 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
1430
1431 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
1432
1433 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
1434
1435 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
1436
1437 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
1438
1439 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
1440
1441 </ul></li>
1442
1443 <li>2018
1444 <ul>
1445
1446 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
1447
1448 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
1449
1450 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
1451
1452 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
1453
1454 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
1455
1456 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
1457
1458 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
1459
1460 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
1461
1462 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
1463
1464 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
1465
1466 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
1467
1468 </ul></li>
1469
1470 <li>2017
1471 <ul>
1472
1473 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1474
1475 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
1476
1477 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
1478
1479 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
1480
1481 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
1482
1483 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
1484
1485 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
1486
1487 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
1488
1489 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
1490
1491 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
1492
1493 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
1494
1495 </ul></li>
1496
1497 <li>2016
1498 <ul>
1499
1500 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1501
1502 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1503
1504 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1505
1506 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1507
1508 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1509
1510 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1511
1512 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1513
1514 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1515
1516 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1517
1518 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1519
1520 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1521
1522 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1523
1524 </ul></li>
1525
1526 <li>2015
1527 <ul>
1528
1529 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1530
1531 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1532
1533 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1534
1535 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1536
1537 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1538
1539 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1540
1541 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1542
1543 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1544
1545 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1546
1547 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1548
1549 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1550
1551 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1552
1553 </ul></li>
1554
1555 <li>2014
1556 <ul>
1557
1558 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1559
1560 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1561
1562 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1563
1564 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1565
1566 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1567
1568 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1569
1570 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1571
1572 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1573
1574 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1575
1576 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1577
1578 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1579
1580 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1581
1582 </ul></li>
1583
1584 <li>2013
1585 <ul>
1586
1587 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1588
1589 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1590
1591 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1592
1593 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1594
1595 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1596
1597 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1598
1599 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1600
1601 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1602
1603 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1604
1605 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1606
1607 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1608
1609 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1610
1611 </ul></li>
1612
1613 <li>2012
1614 <ul>
1615
1616 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1617
1618 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1619
1620 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1621
1622 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1623
1624 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1625
1626 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1627
1628 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1629
1630 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1631
1632 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1633
1634 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1635
1636 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1637
1638 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1639
1640 </ul></li>
1641
1642 <li>2011
1643 <ul>
1644
1645 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1646
1647 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1648
1649 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1650
1651 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1652
1653 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1654
1655 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1656
1657 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1658
1659 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1660
1661 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1662
1663 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1664
1665 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1666
1667 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1668
1669 </ul></li>
1670
1671 <li>2010
1672 <ul>
1673
1674 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1675
1676 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1677
1678 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1679
1680 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1681
1682 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1683
1684 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1685
1686 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1687
1688 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1689
1690 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1691
1692 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1693
1694 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1695
1696 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1697
1698 </ul></li>
1699
1700 <li>2009
1701 <ul>
1702
1703 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1704
1705 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1706
1707 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1708
1709 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1710
1711 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1712
1713 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1714
1715 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1716
1717 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1718
1719 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1720
1721 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1722
1723 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1724
1725 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1726
1727 </ul></li>
1728
1729 <li>2008
1730 <ul>
1731
1732 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1733
1734 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1735
1736 </ul></li>
1737
1738 </ul>
1739
1740
1741
1742 <h2>Tags</h2>
1743 <ul>
1744
1745  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
1746
1747  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1748
1749  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1750
1751  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1752
1753  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
1754
1755  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (13)</a></li>
1756
1757  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
1758
1759  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1760
1761  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (3)</a></li>
1762
1763  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (200)</a></li>
1764
1765  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
1766
1767  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
1768
1769  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
1770
1771  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
1772
1773  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (32)</a></li>
1774
1775  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1776
1777  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (462)</a></li>
1778
1779  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1780
1781  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
1782
1783  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
1784
1785  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1786
1787  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
1788
1789  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1790
1791  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
1792
1793  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (18)</a></li>
1794
1795  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
1796
1797  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (6)</a></li>
1798
1799  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1800
1801  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
1802
1803  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1804
1805  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (6)</a></li>
1806
1807  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1808
1809  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1810
1811  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
1812
1813  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1814
1815  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (46)</a></li>
1816
1817  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (15)</a></li>
1818
1819  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (25)</a></li>
1820
1821  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (324)</a></li>
1822
1823  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (199)</a></li>
1824
1825  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (41)</a></li>
1826
1827  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1828
1829  <li><a href="https://people.skolelinux.org/pere/blog/tags/opensnitch">opensnitch (4)</a></li>
1830
1831  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
1832
1833  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
1834
1835  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (4)</a></li>
1836
1837  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1838
1839  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1840
1841  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1842
1843  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
1844
1845  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1846
1847  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
1848
1849  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1850
1851  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
1852
1853  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1854
1855  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1856
1857  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (76)</a></li>
1858
1859  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
1860
1861  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
1862
1863  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (65)</a></li>
1864
1865  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
1866
1867  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1868
1869  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
1870
1871  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (22)</a></li>
1872
1873  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (80)</a></li>
1874
1875  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1876
1877  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
1878
1879 </ul>
1880
1881
1882     </div>
1883     <p style="text-align: right">
1884  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1885 </p>
1886
1887   </body>
1888 </html>